Changes between Version 2 and Version 3 of Ticket #54426, comment 10
- Timestamp:
- Jul 28, 2017, 3:15:47 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #54426, comment 10
v2 v3 1 1 You can 'lock' or 'peg' a port at certain version fairly easily -- if you already have the version you want to keep, and the new version builds. Just `sudo port selfupdate` and `sudo port upgrade outdated`, and if that works, you can `sudo port activate erlang` and select the older version of `erlang` (or any other port). You're good to go then -- for all intents and purposes, you're locked. IIRC, it won't ask again to upgrade that port, even when new versions come along. 2 2 3 The real problem is when the new version won't build -- then you have a situation. MacPorts will ask over and over for you to upgrade it, and you can't. It often won't build anything else in that case. Similarly, you have a problem if you can't build the current version of a port, but the version three updates back will build on your system.3 The real problem is when the new version won't build, or you don't already have the older version you want installed -- then you have a situation. MacPorts will ask over and over for you to upgrade it, and you can't. It often won't build anything else in that case. Similarly, you have a problem if you can't build the current version of a port, but the version three updates back will build on your system. 4 4 5 5 For THAT issue, you need to make a private local repository and shadow the ports you want to peg at a certain version. It's easy enough to do, but it does have a learning curve.