StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Just a quick clarification about <a href="http://www.macports.org/" rel="nofollow noreferrer">MacPorts</a>. Ayaz is right that, by default, MacPorts will install things in <em>/opt/local</em>. (This makes it easy to globally uninstall later, if you want, and it keeps MacPorts packages out of the way of OS X packages.)</p> <p>When you install MacPorts, it will normally edit your <code>$PATH</code> (and your <code>$MANPATH</code>) for you by updating your user's <em>.profile</em> (creating it, if it doesn't already exist).</p> <p>As a precaution, the installer will create a backup of the original <em>.profile</em> in case you want to roll back the changes (or if you completely uninstall MacPorts later). Here's an example from a random machine at work.</p> <p><code></p> <pre> admin ~ $ ls .profile* .profile .profile.macports-saved_2009-08-03_at_14:55:56 </pre> <p></code></p> <p>If you look in <em>.profile</em> you should see something like this:</p> <p><code></p> <pre> ## # Your previous /Users/admin/.profile file was backed up as /Users/admin/.profile.macports-saved_2009-08-03_at_14:55:56 ## # MacPorts Installer addition on 2009-08-03_at_14:55:56: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts. # MacPorts Installer addition on 2009-08-03_at_14:55:56: adding an appropriate MANPATH variable for use with MacPorts. export MANPATH=/opt/local/share/man:$MANPATH # Finished adapting your MANPATH environment variable for use with MacPorts. </pre> <p></code></p> <p>If your $PATH <em>hasn't</em> been updated, you should adjust it, since otherwise, you will have trouble using the <code>port</code> tool and the software you install via MacPorts.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload