> There is no coherency in how the dependencies are expressed in MacPorts at > the moment: some ports lists all the dependencies recursively while other > ones limit to list only their direct dependencies, as garnome and jhbuild do > the right way. > > This is a mess.
Maybe I'm too ignorant, but isn't also the fact that dependencies are version-agnostic one major cause of build fails and probably a cost-effective gain to change? I'm rather new to macports, but I was delighted to find that it can keep multiple versions installed, with only a single one active (usually) -- only to learn later then that it is otherwise not using this feature, really. So the only workaround is `port -R upgrade', which went into endless looping for mne more than once (I filed a bug [1]). And cleaning the big backlog of obsolete versions does not really work either, as I learned, unless the version is not depended on anywhere or you force it everywhere [2]. Feels like version-awareness might help here sometimes. Florian [1] http://trac.macports.org/projects/macports/ticket/14829 [2] http://www.nabble.com/port-uninstall%3A-dep-check-broken--to16316418.html#a16333096 -- Florian Ebeling [EMAIL PROTECTED] _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
