15 maj 2009 kl. 00.17 skrev Ryan Schmidt:
[...]
As to other ports, most of them probably do not explicitly mention /
sw in their configure scripts.
I'm sure it's a tricky situation for software developers: if they
do add paths like /sw and /opt/local to their configure scripts,
they make it easy for people to install their software manually and
get dependencies from a package manager. However, by doing this,
they make it more difficult to add their software to that package
manager...
Alas, /usr/local/ is where I have most of the stuff (much
"legacy") I'm working with daily. Having to rename /sw and /usr/local
before (sometimes lengthy) upgrading or installing in Macports would
be a major inconvenience.
--
Regards,
/Bjarne.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
