Re: running macports along with homebrew

2018-02-12 Thread Ken Cunningham
If I might suggest something to make this issue easier, If there is anything worth having in MacPorts that is in Homebrew but not MacPorts, just ask for it. Most of these ports take 10 to 20 minutes to make. Some a bit longer, if they are weird in some way. Best, Ken

Re: running macports along with homebrew

2018-02-12 Thread Jeremy Lavergne
On 02/12/2018 09:14 AM, db wrote: > Would it suffice to rename /usr/local during build time to avoid any > conflicts? I ask because I just want to make sure that I'm not missing > anything else. MacPorts can deny any access to Homebrew during builds in trace mode. Less invasive than renaming

Re: running macports along with homebrew

2018-02-12 Thread db
On 12 Feb 2018, at 16:13, Mojca Miklavec wrote: > Exceptions might occur for formulas that put stuff outside of /usr/local AFAIR from the documentation everything that's built locally is contained in so-called cellars under its prefix, so I could just rename it

Re: running macports along with homebrew

2018-02-12 Thread Mojca Miklavec
On 12 February 2018 at 15:14, db wrote: > Would it suffice to rename /usr/local during build time to avoid any > conflicts? I ask because I just want to make sure that I'm not missing > anything else. As far as MacPorts is concerned, I assume it should be mostly OK if you temporarily move

Re: running macports along with homebrew

2018-02-12 Thread db
Would it suffice to rename /usr/local during build time to avoid any conflicts? I ask because I just want to make sure that I'm not missing anything else.