On Fri, Jul 5, 2013 at 11:12 AM, Guido Soranzio <[email protected]>wrote:
> On Jul 4, 2013, at 02:44, Rainer M Krug wrote: > > This would then mean, that two package managers can co-exist, or only > > that macports can work reliably with homebrew installed, but not the > > other way round? > > With the latest Homebrew 0.9.3 it’s quite the contrary. Thanks > to the new “Superenv”, the user’s PATH is ignored completely: > $PATH is only one of the possible problems. Does homebrew prevent promiscuous configure scripts from scanning /sw, /opt/local, etc. for libraries? -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
