At least, "install" and "upgrade" should be consistent. If "install" does not install something, "upgrade" should not touch that either; if "upgrade" would touch something, "install" should install that in the first place. Otherwise, there's too much confusion, and I don't think I'm the only one that is confused.
As for the policy of "including everything in macports", I don't buy it, but it's another story and may be discussed in separate threads. Best Regards, Xin Liu
bin style dependencies are discouraged because of problems like this. The upgrade code (unless you pass it -n, which is what you want to be doing to fix this particular issue for yourself) needs to upgrade library dependencies (for cases where the new version of the port needs the newer library) and can't just check bin/lib style dependencies in that case (as the port could be installed, but is an older version). -- Daniel J. Luke
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
