Does the migration procedure keep ports versions?

[Richard L. Hamilton]

Doubtless someone will correct me if wrong, but I don’t think so. AFAIK, the “port” command cannot install an arbitrary version unaided, only the latest version. But one can go to the repository and fetch an older version of a particular port’s Portfile and use the “port” command with that, and depending on whether it will build with newer versions of what it depends on (or if one manually repeats as needed for them), usually get the older version built and installed. I’ve had to do that a time or two (unrelated to migration), when a newer version was a problem for me, but it’s been long enough ago that I didn’t keep notes, although it has been explained on-list at least once.

An older version might not be possible sometimes esp. across such a big OS version jump, as eventually system headers and interfaces change incompatibly or more likely some are deprecated/eliminated (i.e. anything only 32-bit after Mojave).

AFAIK, the migration procedure does preserve variants and CAN preserve requested/unrequested status.

> On Sep 29, 2022, at 3:58 AM, Ces VLC <cesarillovlc at gmail.com> wrote:
> 
> Hi!
> 
> I'm planning an update of a High Sierra MBP up to Monterey, and I didn't find an explicit mention in the migration docs (https://trac.macports.org/wiki/Migration <https://trac.macports.org/wiki/Migration>) about if the described procedure keeps the ports versions or not. In this moment that's important for me, because I have some compilers (like mingw-w64, for example), and I want to keep them at the same version they are now, because of some compatibility needs.
> 
> Kind regards and thanks a lot,
> 
> César
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20220929/d9c1151a/attachment.htm>