El Capitan and Homebrew

Re:El Capitan and Homebrew by mmastrac on Thursday October 01, 2015 @10:53AM (#10311533)

Ditto. And Homebrew's policy of avoiding installation of built-in packages by default means that you don't accidentally break your whole system when MacPorts shadows a critical core package.

[ Parent | on HN ]

Re:El Capitan and Homebrew by teacup50 on Thursday October 01, 2015 @02:50PM (#10313645)

I can't fathom how MacPorts could ever break your whole system.

- MacPorts' /opt/local is not in any of the default system paths.

- MacPorts uses sandboxing to ensure that builds can't stomp anything outside of /opt/local

[ Parent | on HN ]

Re:El Capitan and Homebrew by jkyle on Monday October 12, 2015 @07:45PM (#10377546)

Not sure about the above poster, but the only times I've heard folks claim that macports broke their system was when they were setting DYLD_LIBRARY_PATH.

edit

should be noted you really ought not do this and if you absolutely have to you should use DYLD_FALLBACK_LIBRARY_PATH

[ Parent | on HN ]

Re:El Capitan and Homebrew by mzs on Thursday October 01, 2015 @02:18PM (#10313332)

Run otool to check but Apple at least builds their stuff right and it's getting harder for companies to shoot themselves in the foot like that cause Xcode automatically does the right stuff for devs that are rushed not careful.

[ Parent | on HN ]

Re:El Capitan and Homebrew by thomnific on Thursday October 01, 2015 @06:34PM (#10315258)

Maybe you didn't know about port select (like me when I started using Macports):

http://stackoverflow.com/questions/6612009/macports-port-sel...

[ Parent | on HN ]