32 ms·

I switched to MacPorts after becoming tired of Brew tainting my filesystem. MacPorts keeps things clean in /opt/. https://www.macports.org/ https://www.macpor

I switched to MacPorts after becoming tired of Brew tainting my filesystem. MacPorts keeps things clean in /opt/. https://www.macports.org/ https://www.macports.org/ https://saagarjha.com/blog/2019/04/26/thoughts-on-macos-package-managers/ https://saagarjha.com/blog/2019/04/26/thoughts-on-macos-pack...

stadeschuldt 3y ago
Nowadays Homebrew keeps its stuff under /opt/homebrew/
- Hamuko 3y ago
  Only if you have an ARM64 Mac. x86 still use the old path.
jwells89 3y ago
I used MacPorts back in the 00s and early 10s but switched to Homebrew when it came out because it was less hassle. Wanted to give it another shot with my latest clean OS install, but wound up installing Homebrew again due to broken packages on MacPorts. Probably should’ve tried to contribute by fixing those packages but didn’t have the time or mental energy available at that point in time.
- pasc1878 3y ago
  How is it less hassle. Installation is similar just a standard mac install. apps are the same. The only difference is that Homebrew gets confused if you install your code or another build in /usr/local oh and Homebrew forces you to use non standard permissions on /usr/local
  - jwells89 3y ago
    Back when I switched, it wasn’t unusual for MacPorts packages to not compile for some reason or another, and at that point my skills in that realm were lacking which meant I had little ability to fix these issues, rendering its technical superiorities over Homebrew moot. Homebrew was less hassle in that most of the time, it successfully installed things and when it didn’t, it was fixed in short order. Since then I’ve become much more capable of diagnosing and fixing broken packages but it’s still not something I’d like to spend my time on if I can help it.
    - pasc1878 3y ago
      Odd I have only had one or two Macports failures

32 ms·

I switched to MacPorts after becoming tired of Brew tainting my filesystem. MacPorts keeps things clean in /opt/. https://www.macports.org/ https://www.macpor

by haykuro 3y ago

stadeschuldt 3y ago
Nowadays Homebrew keeps its stuff under /opt/homebrew/
- Hamuko 3y ago
  Only if you have an ARM64 Mac. x86 still use the old path.
jwells89 3y ago
I used MacPorts back in the 00s and early 10s but switched to Homebrew when it came out because it was less hassle. Wanted to give it another shot with my latest clean OS install, but wound up installing Homebrew again due to broken packages on MacPorts. Probably should’ve tried to contribute by fixing those packages but didn’t have the time or mental energy available at that point in time.
- pasc1878 3y ago
  How is it less hassle. Installation is similar just a standard mac install. apps are the same. The only difference is that Homebrew gets confused if you install your code or another build in /usr/local oh and Homebrew forces you to use non standard permissions on /usr/local
  - jwells89 3y ago
    Back when I switched, it wasn’t unusual for MacPorts packages to not compile for some reason or another, and at that point my skills in that realm were lacking which meant I had little ability to fix these issues, rendering its technical superiorities over Homebrew moot. Homebrew was less hassle in that most of the time, it successfully installed things and when it didn’t, it was fixed in short order. Since then I’ve become much more capable of diagnosing and fixing broken packages but it’s still not something I’d like to spend my time on if I can help it.
    - pasc1878 3y ago
      Odd I have only had one or two Macports failures