Flatpak and SystemD Portable services are actually pretty good.
That's the direction I see Linux going. I personally use NixOS because I am sad.
I looked into Nix but it seemed like it locks you into using bash for your shell. Is that the case?
Sorry I was meaning in the context of using nix-shell for isolated reproducible environments. I read that things can go wrong if you try to use a shell other than bash
Still don't know how I'm supposed to add dictionaries to FF on snap. So many little issues like this with snaps.
Tar is not a package manager, it is just a packaging format. AppImage has the same problem.
Flatpak is a bit of a crappy package manager but at least it is one. And, due to its use of container technology, it allows the same packages to run on any Linux kernel (any Linux distro). That is pretty useful.
Of the other package managers, apk 3 is my favourite but the only distro that uses it is Chimera Linux. Pacman is good. dnf / RPM is ok. apt / deb is in last place for me. The recent Ubuntu 25.04 launch snafu illustrates some of the problems with apt. The first Linus Tech Tips Linux challenge really highlighted the dangers of apt.
I only used snap briefly but instantly hated it. Fstab was a mess. It was slow. It was proprietary. I fled before I could form an educated opinion.
it allows the same packages to run on any Linux kernel (any Linux distro). That is pretty useful.
flatpak itself depends on namespaces, so saying that it works on any kernel is quite a stretch.
Can flatpak do this? This is a GIMP3 appimage running on ubuntu 10.04 without any container:
The kernel is so old that even the appimage runtime itself complains of missing functions and has to fallback to a workaround.
UPDATE: flatpak can't work because bubblewrap itself can't:
PR_SET_NO_NEW_PRIVS is only available since kernel 3.5
Nix is just across the street sipping tea because it understands what it is and is at peace with the chaotic world around it.
Gentoo is too busy compiling to notice what's going on around it
If you want, you can also compile everything with Nix!
Let the hate of the crowd wash over me, but I don't even like Flatpak, and I've got love-hate (mostly hate) relationship with AppImage as well.
Just give me a system package or a zipped tarball.
In recent years, have had to just get used to needing to build most projects from source.
Are there enough watermarks on this meme? At least we got reddit covered.
AppImage is the no-nonsense universal package format.
AppImages have a lot of problems
Last time I read something from the main dev I almost ran stright into the woods.
Also idk about how it is the management situation, portals integration, etc…
It's not about the package management method that we use. It's about the friends and enemies we made along the way (while arguing about package management.)
Haha, I break snap a lot less than the others, and it took a bit to figure out the differences. Appimages are annoying af. Flatpaks are my favourite when there isn't a good old .deb. I recently broke Flatpak though so it's on my naughty list. Snap still chugging along for some reason, I just wish the permissions weren't so crazy strict (Nextcloud).
Speaking of all this, I realised I've accidentally installed some things twice. Is there a good way to list all the different package managers together to see what is duplicated?
How do you break a flatpak?
I once uninstalled a flatpak and it rendered another installed flatpak unlaunchable. Not even the repair function would fix it. Ended up having to use timeshift to rollback. Not sure if that was the fault of Flatpak or that one specific app but it was pretty frustrating.
Asking the real questions here.
A stab at my personal ranking: .deb > appimage > flatpack > curling a shell script
I can't help but love a .deb file (even when not via repo), I've almost exclusively used Debian and it derivatives since the late 90s. And snap isn't on the list because it got stored in a loopback device I removed.
If flatpak didn't make me put the entirety of KDE onto my system (thats an exaggeration but you know what I mean) I'd gladly crown it king of the package managers.
I just want to point out the dependencies of Konsole (arguably a small and simple application in concept): glibc gcc-libs icu kbookmarks kcolorscheme kconfig kconfigwidgets kcoreaddons kcrash kdbusaddons kglobalaccel kguiaddons ki18n kiconthemes kio knewstuff knotifications knotifyconfig kparts kpty kservice ktextwidgets kwidgetsaddons kwindowsystem kxmlgui qt6-5compat qt6-base qt6-multimedia sh.
Plus make it hell on earth to a) access drives other than the one flatpak is installed on, b) interoperate with non-flatpak applications, and c) retain any amount of free space on my drives (exaggeration for effect).
Psst .. the first KDE app you installed via your package manager also put "the entirety of KDE" onto your system.
my issue with snaps is honestly just that they are controlled too much by just one entity (canonical) and there is no reason for them to exist because flatpak already does everything they do.
I have really started to like AppImage. You just download a single file make it executable and it just works.
I use Cursor for coding, and it has an appimage that replaces itself when it updates.
That's cool and all but it would be even cooler if you could just install and keep it updated through your package manager
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.