[MacPorts] FAQ modified

[MacPorts]

Changed page "FAQ" by ryandesign at macports.org from 70.114.141.44*
Page URL: <https://trac.macports.org/wiki/FAQ>
Diff URL: <https://trac.macports.org/wiki/FAQ?action=diff&version=123>
Revision 123
Comment: minor edits

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FAQ
=========================================================================
--- FAQ (version: 122)
+++ FAQ (version: 123)
@@ -53,31 +53,31 @@
 === Why is /opt/local the default install location for MacPorts? === #defaultprefix
                         
 Traditionally, the place to install third party software on many UNIX systems is `/usr/local`.
-However, having macports under `/usr/local` would be error-prone for precisely that reason.  
+However, having MacPorts under `/usr/local` would be error-prone for precisely that reason.  
 Many other software packages and packaging systems install into `/usr/local`,
-and could accidentaly overwrite what macports has installed, or vice versa.
+and could accidentaly overwrite what MacPorts has installed, or vice versa.
 
 While this could be dismissed as the user's own error, it is a fact that
 people click through installers blindly, and consequently collisions under       
 `/usr/local` (and other prominent directories) happen very often.
-Macports doesn't want to be a victim of that, and `/opt/local` provides
+MacPorts doesn't want to be a victim of that, and `/opt/local` provides
 the splendid isolation (as would any other dedicated directory, of course).
 
 Also, `/usr/local` traditionally contains the given system's local admin tools;
-macports doesn't want to stomp on that either.
+MacPorts doesn't want to stomp on that either.
 
 (For the same reasons, fink uses `/sw` as its prefix.)
 
-=== So with macports under /opt/local I can use /usr/local freely? === #usrlocal
+=== So with MacPorts under /opt/local I can use /usr/local freely? === #usrlocal
                                                                                 
-No, not entirely. Even with macports living elsewhere, `/usr/local` can still interfere.
+No, not entirely. Even with MacPorts living elsewhere, `/usr/local` can still interfere.
 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 probably be adviced to temporarily rename
+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 probably be advised to temporarily rename
 `/usr/local` to make it disappear entirely for the duration of the build.
-Obviously, this wouldn't be possible to do if macports itself lived under `/usr/local`.          
+Obviously, this wouldn't be possible to do if MacPorts itself lived under `/usr/local`.          
  
 === How do I remove or uninstall MacPorts? === #uninstall
 

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on FAQ. If it was not you, please
report to .