17 ms·
You can use Homebrew and MacPorts concurrently. I will always choose the MacPorts version of a tool given the option and only fall back to a Homebrew version w
by bmurphy1976 5y ago
You can use Homebrew and MacPorts concurrently. I will always choose the MacPorts version of a tool given the option and only fall back to a Homebrew version when absolutely have no other choice. It's frustrating to have to use two tools but I've found it easier to keep my dev environment clean this way.
- leucineleprec0n 5y agoWait; do you mind sharing a bit more about how you do this? I somehow missed this reply, and appreciate the pointer
- bmurphy1976 5y agoI haven't had to do anything fancy yet. I just install both and try to find the MacPorts equivalent first before using Homebrew. For example, I use the MacPorts version of Python. If I need any Python dependencies I install them either via MacPorts or pip. In fact, I only have two Homebrew packages installed: dockutil and mas. Both are tools I use as part of ansible scripts which don't have MacPorts equivalents. All the remaining Homebrew packages are all cask apps (Firefox, Chrome, Discord, Slack, etc.). Those don't have any dependencies that would cause any conflicts. For comparison, I have 139 MacPorts packages installed. 2 Homebrew packages, and 21 Homebrew cask apps.