On 2014-02-12, at 3:50 PM, Art McGee wrote:
> On a related note, Homebrew is actually based on GNU Stow. It's basically a
> clone/ripoff with enhancements. If you're going to use Homebrew, then use it
> in the same way suggested for Stow, and install packages in your home
> directory, leaving /
On Fri, Feb 14, 2014 at 12:56 PM, Gregory Shenaut wrote:
> I've been reluctant to use anything under /opt because in the event I ever
> need to scrub macports and start over, it's easier to remove /opt and
> reinstall macports from scratch.
>
Other third party software uses /opt as well (and even
On Feb 14, 2014, at 11:56, Gregory Shenaut wrote:
> On Feb 14, 2014, at 08:46 , Mark Anderson wrote:
>
>> I also install into /opt/ where 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 pl
On Feb 14, 2014, at 08:46 , Mark Anderson wrote:
> I also install into /opt/ where 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 w
I also install into /opt/ where 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 cour
Hi,
> So let's be a little more specific. You are saying that it's
> /usr/local/include and /usr/local/lib that are the problem, not
> /usr/local/bin, right? Otherwise you're saying that, for example,
> MacPorts is incompatible with BBEdit (which puts symlinks in
> /usr/local/bin). Very few "or
On Feb 12, 2014, at 18:46, Mike Alexander wrote:
> --On February 13, 2014 1:24:57 AM +0100 Clemens Lang wrote:
>
>> If those binary installers did install headers in /usr/local/include
>> and libraries in /usr/local/lib that has been pure luck. As soon as
>> you install a port that has an option
On Feb 12, 2014, at 18:24, Clemens Lang wrote:
>
>> export MANPATH="/opt/local/share/man:${MANPATH}"
>> export INFOPATH="/opt/local/share/info:${INFOPATH}"
>
> As far as I know those aren't used on newer versions of OS X and are
> automatically derived from the value of $PATH.
As far as I know
--On February 13, 2014 1:24:57 AM +0100 Clemens Lang
wrote:
If those binary installers did install headers in /usr/local/include
and libraries in /usr/local/lib that has been pure luck. As soon as
you install a port that has an optional dependency not installed via
MacPorts but present in /us
Hi,
> Actually, I don't think there is that much of a problem with installing
> software in /usr/local, the problem is the particular way that Homebrew does
> it by default, taking over /usr/local completely, and it's disregard for
> standard ownership and permissions.
You're wrong on that one. T
> 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?
>
Actually, I don't think there is that much of a problem with installing
software i
On Wed, Feb 12, 2014 at 10:04 AM, Gregory Shenaut wrote:
> 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?
I install everything int
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?
Greg Shenaut
___
macports-users mailing list
13 matches
Mail list logo
