[MacPorts] FAQ modified

MacPorts noreply at macports.org
Fri Nov 13 23:11:14 PST 2015


Page "FAQ" was changed by ryandesign at macports.org
Diff URL: <https://trac.macports.org/wiki/FAQ?action=diff&version=143>
Revision 143
Comment: add libraryframeworks section similar to usrlocal section
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FAQ
=========================================================================
--- FAQ (version: 142)
+++ FAQ (version: 143)
@@ -73,14 +73,14 @@
 
 (For the same reasons, fink uses `/sw` as its prefix.)
 
-=== So with MacPorts under /opt/local I can use /usr/local freely? === #usrlocal
+=== Can I install software in /usr/local while using MacPorts? === #usrlocal
 
 No. Even though MacPorts is installed elsewhere, software installed in `/usr/local` can still interfere with MacPorts.
 Some software (especially the GNU auto* tools and gcc) looks into `/usr/local` for external headers, libraries, and binaries. Certain ports might (and do) fail to build because during their build something incompatible is found and picked up
 from `/usr/local`. Good ports avoid this by explicitly specifying `--with-libfoo=/opt/local/lib/` or explicitly disabling all such possible dependencies altogether with `--disable-foo` or `--without-bar` but not all ports are able to do that.
 
-If you ask on a MacPorts mailing list about a port failing to build because it chokes on something
-that it found and picked up in `/usr/local` you will be asked to remove what you've installed in `/usr/local`
+If you ask us for help with a port failing to build because of something
+that it found in `/usr/local` you will be asked to remove what you've installed in `/usr/local`
 or to temporarily rename `/usr/local` to make it disappear entirely for the duration of the build.
 
 Note that starting with 2.3.0, MacPorts can automatically hide `/usr/local` (and all other files a port does not depend on) from ports' build systems.
@@ -92,6 +92,15 @@
 
 Note that trace mode in MacPorts 2.3.4 and earlier is not compatible with El Capitan.
 A fix has been committed in r141420 but not yet released in a stable version of MacPorts.
+
+
+=== Can I install frameworks in /Library/Frameworks while using MacPorts? === #libraryframeworks
+
+No. This can interfere with software you want to install with MacPorts, in much the same way that [#usrlocal installing software into /usr/local] can interfere. 
+If you ask us for help with a port failing to build because of something
+that it found in `/Library/Frameworks ` you will be asked to remove what you've installed in `/Library/Frameworks `
+or to temporarily rename `/Library/Frameworks ` to make it disappear entirely for the duration of the build.
+
 
 === How do I remove or uninstall MacPorts? === #uninstall
 
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/FAQ>
MacPorts <https://www.macports.org/>
Ports system for OS X

This is an automated message. Someone added your email address to be
notified of changes on 'FAQ' page.
If it was not you, please report to .


More information about the macports-changes mailing list