> I not referring to that. Rather I am concerned about the case where > libpng and a number of packages that require it are already installed. > If the user does a 'sudo port selfupdate' and 'sudo port outdated', what > insures that none of the packages being upgraded aren't built before the > new soversion of libpng is installed? The absence of any checks for > version dependencies in MacPorts appears to make that impossible. It is > very unfortunate that the depends-lib file doesn't allow for a syntax > like... > > depends-lib: port:libpng(>=1.4) > > or > > depends-lib: port:libpng(>=1.4.5-1) > > such that port could attempt to order the build such that the version > dependencies are met.
Building follows the dependency tree, which handles this, doesn't it?
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
