4 ms·

I used to be cranky about it taking over /usr/local but since I upgraded to an M1 I have no problem with it hanging out in /opt. I don’t understand why the path

I used to be cranky about it taking over /usr/local but since I upgraded to an M1 I have no problem with it hanging out in /opt. I don’t understand why the path switched when the architecture did but I’m happy about the change.

frizlab 4y ago
I think it’s easier to maintain the bottles for two different architectures at two different paths, and the /usr/local path take over was a recurrent complaint, so the devs took advantage of the new arch to change the path.
- Hackbraten 4y ago
  Ex-Homebrew maintainer here. You’re correct. I couldn’t have explained it better.
fijiaarone 4y ago
Brew moving to /opt was nice on M1 but nothing being able to compile on M1 is a bit inconvenient. But that’s not brew’s fault.
- mdaniel 4y ago
  I mean, that can't possibly be true, right? The bottles don't appear out of nowhere. So "brew install --build-from-source bash" dies for you?
- jordemort 4y ago
  Not sure if your issue is brew-specific, I've compiled plenty of stuff since getting my M1
acdha 4y ago
No legacy systems meant they didn’t have to worry about whining when they switched since everyone was by definition using a new install.