3 ms·
It’s a strategy. Package managers have to choose a strategy: slow, crusty and stable or bleeding edge? It’s not CentOS… it’s a local dev machine. The same scena
by whalesalad 5y ago
It’s a strategy. Package managers have to choose a strategy: slow, crusty and stable or bleeding edge? It’s not CentOS… it’s a local dev machine. The same scenario will occur on Arch Linux.
Fortunately Homebrew has lots of helper scripts to upgrade DB’s like Postgres. You probably saw some scroll back with a command to upgrade from 12 to 13 or 13-14 etc. It will even download and install an old version in order to upgrade safely.
I understand the frustration but what is the alternative? Pinning every dependency? The reason so many of your packages were updated was likely because a core dependency was upgraded like OpenSSL.
- ryandrake 5y agoIt would be nice if you could run Homebrew in a mode where dependencies were statically linked if possible. On my system, "brew list | wc" shows 200 installed packages, and "brew leaves | wc" shows that I actually only intended to install 32 of them. This is a huge dependency tree full of junk I don't even know if I actually need. Static linking would save a lot of space and make your list of installed packages simpler and more understandable.
- kbutler 5y agoIn my experience, developing software on a local dev machine is precisely when fine-grained control of software stack versions is needed. This can be encapsulated with things like docker, but the "I'll globally, arbitrarily update everything to the bleeding edge" strategy isn't friendly for building and maintaining software.
- whalesalad 5y agoThat capability exists: brew install postgres@12