On Jan 6, 2014, at 12:37, Peter Brommer <[email protected]> wrote:
> I ran into a problem running port upgrade outdated today. Among the packages > to be upgraded were libLASi (from 1.1.1_0 to 1.1.1_1) and graphviz (from > 2.34.0_1+pangocairo+x11 to 2.34.0_4+pangocairo+x11). However, the port > upgrade command chose to execute the upgrade in an unfortunate sequence: > First it tried to upgrade graphviz, which failed due to the bug in ticket > https://trac.macports.org/ticket/41567 - That ticket is about libLASi, not graphviz, and was resolved 6 weeks ago. > when the proper behaviour would have been to upgrade libLASi first. This > required a manual intervention, which IMHO is not user friendly. > > Does the port upgrade command have any logic in determining the order of > upgrades? Or is this something that needs to be specified on the port file > level? In this case, graphviz lib-depends on libLASi, so should port not try > upgrading the deps before a package? It does. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
