3 ms·

> Homebrew still chugging along. For seven years longer and with 20K more ports than Homebrew, and without leaving a mess on your system or munging permissions

• snazz 4y ago
  Does Homebrew still have those issues on newer Macs with the /opt/homebrew prefix? I don’t use either at the moment but last time I looked at Homebrew it looked like they had changed the way it installed, at least on Apple silicon Macs.
  • philistine 4y ago
    The default install location for Apple Silicon and Intel is different, for some reason. I got weird problems when many bottles were still Intel-only, but now everything is good. So unless you hate /opt/homebrew, it’s great!
  • OmarAssadi 4y ago
    I'm using Nix now on my macOS installs, so I might not be totally correct the current situation. But yeah, I believe most of those sorts of issues have gone away with the new prefix. There's still some weird annoyances for me, though. For example, it's still intended for single-user mode only. The best solution I came up with was to create a separate user for Homebrew and then basically alias `brew` to `sudo -H -u homebrew brew`. And generally, if you attempt to use a non-standard prefix, such as in your home directory, packages will have to be built from source. I understand why, but it sucks because this means when you need x86-only packages via Rosetta, you're stuck with the old `/usr/bin` prefix, unless you want to and can build from source. Also, in general, maintaining multiple prefixes/architectures is annoying too. I wish the default command allowed me to just pass `--arch amd64/arm64` or something when installing packages