<div dir="ltr">I also install into /opt/<something> where <something> expands to something descriptive of all the crap I am installing in there. Then I can turn PATHs on and off depending. This is really important for playing with things like the gtk+ cocoa that needs its whole space to itself. Just DONT use /opt or /opt/local of course. I also set them to be owned by my user, so I don't have to sudo to install. If I do, I know something is up.<div>
<br></div><div>Mark</div></div><div class="gmail_extra"><br clear="all"><div>—Mark<br>_______________________<br>Mark E. Anderson <<a href="mailto:emer@emer.net" target="_blank">emer@emer.net</a>><br></div>
<br><br><div class="gmail_quote">On Wed, Feb 12, 2014 at 10:56 AM, Arno Hautala <span dir="ltr"><<a href="mailto:arno@alum.wpi.edu" target="_blank">arno@alum.wpi.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On Wed, Feb 12, 2014 at 10:04 AM, Gregory Shenaut <<a href="mailto:gkshenaut@ucdavis.edu">gkshenaut@ucdavis.edu</a>> wrote:<br>
> I understand why installing in /usr/local can mess up macports, but macports doesn't have everything, and most third-party software wants to go into /usr/local. Where should this stuff go, if not /usr/local?<br>
<br>
</div>I install everything into my home folder.<br>
<br>
> ./configure --prefix=~/local/<br>
> make && make install<br>
<br>
If you need it available system-wide, just pick some other custom<br>
location (ie. /custom/). In any case, just make sure you're consistent<br>
(update your PATH) and point your configure script to the right place<br>
if the software can't find the libraries in your path or you need to<br>
override libraries that are in your path.<br>
<br>
The longer answer is that I use stow<br>
(<a href="http://www.gnu.org/software/stow/" target="_blank">http://www.gnu.org/software/stow/</a> ; and available in MacPorts) to<br>
assemble the bin, man, etc. directories. Stow isn't required, but it<br>
does help manage the software that isn't being managed by MacPorts.<br>
So, I might install a piece of software with:<br>
<br>
> ./configure --prefix=~/local/stow/foo-1.2.4<br>
> make && make install<br>
> cd ~/local/stow<br>
> stow foo-1.2.4<br>
<br>
Stow just allows you to easily add and remove versions of software by<br>
linking a hiearchy of directories into a common location. I might have<br>
foo-1.2.4, foo-1.2.6, bar-3.9, but only have foo-1.2.4 and bar-3.9<br>
active. I can the upgrade to foo-1.2.6 by running:<br>
<br>
> cd ~/local/stow<br>
> stow -D foo-1.2.4<br>
> stow foo-1.2.6<br>
> rm -rf foo-1.2.4<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
arno s hautala /-| <a href="mailto:arno@alum.wpi.edu">arno@alum.wpi.edu</a><br>
<br>
pgp b2c9d448<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
macports-users mailing list<br>
<a href="mailto:macports-users@lists.macosforge.org">macports-users@lists.macosforge.org</a><br>
<a href="https://lists.macosforge.org/mailman/listinfo/macports-users" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-users</a><br>
</div></div></blockquote></div><br></div>