3 ms·
I realize this is a bit counter to the thread title but can someone who’s familiar with macports give their take on whether it’s worth using both brew + macport
by upbeat_general 6y ago
I realize this is a bit counter to the thread title but can someone who’s familiar with macports give their take on whether it’s worth using both brew + macports at once is a good idea?
I’ve been solely using brew and very much appreciate the convenience but I saw that macports allows multiple versions of a single package which has been a pretty big pain point for me with brew.
It doesn’t happen super often but there have been several times that this limitation for brew has been a huge pain point, forcing me to pollute things by compiling manually, putting it in a new location, etc.
I know it’s a bit far fetched but if my package manager could replace say, pyenv, by just making it easier to install several different versions and then letting me pick the default symlink, that would be so helpful (or even just not removing python2...).
- saagarjha 6y agoHomebrew and MacPorts tend to not do well because Homebrew installs itself to /usr/local, which is on PATH by default and can cause strange build failures for other things. However, with the new prefix it might be possible to do this better now.