Hi,
I thought the whole reason for living under /opt/local was *not* to
interfere with /usr/local. How exactly does having /usr/local interfere?
Things from macports silently picking up things from /usr/local?
Is that the problem?
The issue is some packages have hard coded dependencies to look for
things in /usr/local, and will use them if found. Most packages are
developed on linux OSes, where /user/local is quite normal and thus they
just consider this the 'right thing to do'... In principle packages
should provide options to avoid this, and when they do MacPorts can use
them, but not all do.
I don't install things there, but there are things in there
(mostly from Mac OS) that I'd like to keep and use.
Yes, I have things in /usr/local too - stuff that is _not_
in macports (otherwise I would just install it from macports - and
have it installed under /opt/local), and local admin tools.
It would be a PITA to make that disappear during every
macports action (not that it's very often) ...
Perhaps the best advice is, if you find a package you need not in
MacPorts, to build a port file for it and submit it for inclusion ;)
Chris
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
