Versions in ports

Artur Szostak aszostak at
Mon Sep 14 09:51:40 PDT 2015

>> […] A normal upgrade will first upgrade all the ports
>> dependencies, as required, such that you end up with a consistent
>> updated port. Only if you specifically disable this can you get into a
>> mess.
> But if ports A and B both depend on port C, and you run “port upgrade
> A”, then it will upgrade C as well, if necessary, but then what about B?
> Concerns like this is one reason why I never upgrade ports individually,
> but rather just run “port upgrade outdated” instead.

Without having a mechanism to encode versions into the dependency
information of Portfiles, it is impossible to make the following command
    sudo port upgrade <port-name>

Something feels amiss.

More information about the macports-users mailing list