How to use macports and homebrew package management systems together without having them interfere with each other in bad ways?
How to use macports and homebrew package management systems together without having them interfere
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
It’s best to use just a single package manager and uninstall the others. If, for example, you want to use MacPorts, but there’s a program you need that’s not in MacPorts, consider filing a MacPorts port request ticket.
If you insist that you must install multiple package managers, then please install all of them in nonstandard prefixes. MacPorts’ default prefix is /opt/local. Homebrew defaults to /usr/local. Fink uses /sw. Build each package manager from source manually, selecting a unique install prefix for each that is different from all of the preceding default paths. This is to ensure that software packages that have hardcoded knowledge of these package managers’ default paths do not inadvertently find dependencies from the wrong package manager.
When you install a port with MacPorts, it clears most environment variables; this is to ensure that, even if you have, say, /usr/local/bin and /sw/bin in
$PATH, MacPorts will not find things there. I don’t know whether Homebrew and Fink do this too; if they don’t, change your$PATHso that it doesn’t contain locations with potential third-party dependencies, before you install anything using Homebrew or Fink.