Context Navigation

Changes between Version 4 and Version 5 of Ticket #54426, comment 10

v4	v5
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 -- 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 (or don't want) the current version of a port, but the version three updates back will build on your system or is the version you need.
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.