How about a system where you can keep around multiple versions of a library. If you update a library you could then relink applications to use the newer version if they can handle it. The old library would still be around to everything that needs it can still use it.
Version the libraries in a way where minor bumps don't break or change the interface so no breakage should occur in any software that uses it. That you you also shouldn't have to keep a whole slew of minor versions around.
Let me guess Zig Forums, I just reinvented some idea from the 60's right?
Liam Roberts
That's called Gentoo. It's what SLOTs are for.
Jason Mitchell
But isn't it great that you can use an OS developed in a completely ad-hoc way through the marketplace of ideas, where everyone and his dog can commit code? I mean, between that and a system developed by a small, dedicated, and competent team with a clear vision of how it should work, which would you choose?
Only 2 things I don't like about Linux: takes too long to "get it right," screen tearing was gay without a lot of fucking around.
Other than that I can use Krita and Blender and make a living so it's fine.
Nathan Gutierrez
It is a real problem though, just five minutes ago I downloaded old package of aegisub (same aegisub version) from Debian stable because Debian testing fucked up aegisub (same version since 2014). I do it like this though which is a bit of work, but not much.
I have a folder $HOME/apps and the /usr/bin shit under that. I got aegisub, and after runnning it figured out I needed to get older hunspell and libass. Just dpkg -x packages.deb $HOME/apps and then "patchelf --set-rpath '$ORIGIN/../lib/x86_64-linux-gnu' aegisub-3.2".
No copilochacho neccesaburrito!
Nolan Perez
I think "UNIX Hater's Handbook" should be on Zig Forums's obligatory reading list. You don't even need to agree with it, it's just fun look into history of Unix development.
