5 ms·

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 sh

• mzs 11y ago
  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.
• teacup50 11y ago
  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
  • jkyle 11y ago
    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
• thomnific 11y ago
  Maybe you didn't know about port select (like me when I started using Macports): http://stackoverflow.com/questions/6612009/macports-port-select-commands http://stackoverflow.com/questions/6612009/macports-port-sel...