I’m getting tired of all of these new, supplementary package formats.
I’m a recent (< 2 years) convert to RPM style packages, coming from the world of Slackware and it’s derivatives. Dependency tracking, one command installs, and assurances of compatibility are all relatively new things to me, and I’m not exactly resistant to that change anymore. I’m glad to leave dependency hell behind.
However, what I’ve come to think of as “meta-package managers” have recently emerged: systems which allow You to install software outside of Your package management system, but within their own. Sounds stupid at first blush, but there are a few cases where it makes a lot of sense.
For instance, on an episode of Late Night Linux, one of the hosts mentions Steam as a good use case for Snaps. This makes perfect sense, since all the packages do is download the runtime anyway. Self contained systems like that, that cannot rely on the environment already present on Your machine, are a great candidate for this kind of installation.
Taking a step back, I’m one of those people who heavily uses
and company to install software which is unpackaged. Most of my
in-progress scripts live there, as well as any “extract and run
from the directory” software. I also used to put my texlive
distribution there. So, the idea of ‘installing’ software outside of a
package management scheme isn’t completely alien to me.
However, the idea of these kinds of things being integrated into the GUI package manager used by the system (like in Ubuntu, where the Snap and the deb are listed one after the other with no distinguishing marks) is just asking for trouble. Both from the obvious end-user fiasco (that I experienced while getting my father on Ubuntu) and from another, more problematic angle.
If we rely on this kind of thing too much, we’ll just end up in the same situation as before, but with three new package managers that don’t care which distro You are running.
I think the reason these systems work so well right now is that there are so few packages installed by them. Once a critical mass is reached, You won’t be able to use this package and that package at the same time, because they rely on different, incompatible versions of the same library. Trying to police that means making choices about what can be in the package manager, which is where RPMs, debs, and others are now.
I’m just frustrated right now, because I’ve had to switch Messenger for Desktop out for Caprine. Messenger for Desktop had the normal slew of *nix packages, whereas Caprine only has .deb and AppImage. That’s troubling to me, and I hope it does not become a common practice. I don’t want to go back to compiling everything myself.Categories: Computers
Tags: packages  foss  linux