On Mar 6, 2009, at 15:37, Orville Bennett wrote:
Is there some check which ensures that upgrading the dependency
doesn't break the app that's updated?
I don't understand the scenario. Could you give an example?
What the commit is supposed to fix is the following case:
foo depends on bar.
You already have bar 1.0 installed but you don't have foo installed.
bar 1.2 is available in the ports tree.
Prior to this commit, if you "port install foo", the latest version
of foo gets installed but bar remains at 1.0.
The latest version of foo may not be compatible with bar 1.0 but
should be compatible with the latest version of bar, 1.2.
After this commit, if you "port install foo", bar first gets updated
to 1.2, then foo gets installed.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
