14 ms·
I quit using homebrew after the auto-update-everything kicked in as part of installing some new tiny utility. Both Apple and homebrew had transitioned away from
by password4321 4y ago
I quit using homebrew after the auto-update-everything kicked in as part of installing some new tiny utility. Both Apple and homebrew had transitioned away from supporting my OS recently... several working versions of software were uninstalled, then something failed to build, leaving behind a total disaster.
I wouldn't even consider using it again without HOMEBREW_NO_AUTO_UPDATE=1. MacPorts has been good to me, it even has an ncdu1 package since Zig doesn't support legacy macOS either.
Ask HN: Best Alternative to Homebrew in 2021?
https://news.ycombinator.com/item?id=29079096 https://news.ycombinator.com/item?id=29079096
- laserlight 4y agoI wonder who thought the autoupdate is a good idea. It's absolutely crazy. Lots of things break down and some of them do silently, making it really difficult to find the problem when one discovers it days or weeks after the autoupdate.
- acdha 4y agoOn a clean system it’s rare to have things break so if you’re an open source developer you prefer people use the current release of something rather than re-reporting bugs you fixed 3 years ago.
- hparadiz 4y agoThank you for this little bit of sanity.
- pgorczak 4y agoSeconding this, I have lots of Python virtual environments with packages that link to brew libs. It’s a bummer coming back to an env after a while and then realizing auto update has removed linked files due to a minor version bump
- rjzzleep 4y agoI used gentoo prefix for a long time and it was a much much better citizen than homebrew(which isn't hard TBH). But gentoo has a terrible way of engaging the community. I tried to contribute but it was just cumbersome. So in the end back in the days I still had my own clang patches(basically before all the apple changes were upstreamed).