deps that are installed in non-/opt locations
How does MacPorts keept track of packages installed on the system that aren't in /opt/local/, like X11. I am wondering, because rather then making use of the autoconf and automake that are already in OS X with the developer tools installed, MacPorts builds its own.
On Oct 2, 2006, at 11:09, Sancho McCann wrote:
How does MacPorts keept track of packages installed on the system that aren't in /opt/local/, like X11. I am wondering, because rather then making use of the autoconf and automake that are already in OS X with the developer tools installed, MacPorts builds its own.
The reason MacPorts builds its own versions of things Apple already provides is explained here: http://trac.macports.org/projects/macports/wiki/ FAQ#WhyisMacPortsusingitsownlibraries
participants (2)
-
Ryan Schmidt
-
Sancho McCann