3 ms·
Nobody knows how to use the package manager. What happens in practice, is every single program uses the the package versions the distro happens to ship with. I
by torginus 2y ago
Nobody knows how to use the package manager. What happens in practice, is every single program uses the the package versions the distro happens to ship with.
If you want a newer version, too bad - your OS doesn't ship that so better luck in the next release. OR you can set up a private repo, and either ship a binary that has the dependencies included (shipping half the userland with your audio player), or they package the newer version of library, which will unwittingly break half your system, if not today, then surely at the next distro upgrade.
It speaks volumes of Linux package management woes, that no vendor ships anything analogous to brew or chocolatey.
- gugagore 2y agoI thought it spoke to windows and macOS woes that package management was a third-party concern. What is the gap between e.g. `apt` and Homebrew?
- torginus 2y agoThere are the following differences usually: - Packages are useful units of software in homebrew, and both end-user apps dependency libraries in apt (and weird stuff, like headers, or dependencies) - Homebrew packages are installed for the user, apt is system-wide - Homebrew packages are updated and maintained usually by people involved with the software they are shipping, apt packages are usually maintained by the distro - As a result, Homebrew packages almost always work and are almost always up to date, apt ones are almost never (stuff like go, node etc.) Apt is like a weird frankenstein monster of npm, the system update, and an app store, and all that with a global scope.