Ive just gone to update my flatpak. I now have to download 7 slightly different versions of nvidia drivers. 7 Fucking times the same Nvidia driver. 7. 7 Goddamn times.
And no, I dont want to hear your excuses for this. I dont care if it only downloads 370 Mbs instead of 371.
It’s almost like this is the point of flatpak
Where is the meme?
Nvidia drivers
Nvidia
Makes sense
flatpak remove --unusedAny idea why flatpack doesn’t remove unused (automatically installed) dependencies automatically or at least give a hint, as e.g.
aptdoes?And if that doesn’t work, just remove the nvidia drivers that do not match the installed version. It may give you a warning that the package is in use but it shouldn’t be an issue if you (OP) keep the version that matches your driver
mfw
flatpak removedoes not remove flatpakDoes
apt removeremove apt?
Why are you even using flatpak if its core usecase offends you?
Why are you even using flatpak if its core usecase offends you?
That meme doesnt really work the way you want it to here. I get what you’re going for but that’s one hell of a stretch.
The more I learn about flatpaks, the more I wonder what the fuck happened to APT GET that it was necessary to have everything in one package. Apt would grab dependencies, too, if they were necessary the last time I was heavily using Linux. Is that no longer the case?
Flatpak is not just an alternative packaging format. One of the key advantages is that it provides a predictable runtime environment that is independent from the rest of the system. Sometimes an application needs a particular version of a dependency (called dependency pinning, very common practice in development) and can’t rely on the system having the correct files. It also isolates the application from issues stemming from environment variables and the “global” filesystem.
It also gives developers greater control over packaging. Because of this isolation, they don’t have to rely on downstream packagers to manually adapt the software to the distro’s available packages (potentially introducing bugs).
One infamous example is Bottles. The project is officially distributed as flatpak, but OpenSUSE wanted to distribute it as native binaries. They had to use an outdated, broken version and caused a flood of user reports for issues that were not Bottles’ fault. More in this thread and open letter: https://github.com/bottlesdevs/Bottles/pull/3583
This. Once you know how to use it it’s way, way more preferable than dealing with all the problems that come from how scattered the Linux ecosystem is and how little control you as a dev had about app distribution. Development and debugging gets more predictable, people can get (app-related) fixes faster, it’s hypothetically more secure (if Flatpak gets their shit together) and with the payment backend for Flatpak repos they (Gnome Foundation & KDE e.V.) work on it finally becomes properly viable to distribute paid apps. All the different hacky ways that are currently circulating (which are often outdated, only work on certain distros etc.) to offer paid applications are honestly obnoxious and expensive to maintain. Not to mention Flatpaks work great on immutable distros.
Just hope they gonna moderate things properly. Flathub & perhaps a few others have to place themselves as the de-facto standard marketplace to define and uphold all the important values the Linux community is organized around once it gets commercial. Not to do so would be a phenomenal mistake and end up in enshittification once the tech bros start targeting Linux.
So yeah, Flatpaks, Snaps and (maybe) AppImages are probably the future for most common end-user distros. Sorry for the small tangent.
Two big reasons I know of are dependency conflicts (not a thing with flatpak…i.e. package A requires one version of lib, package B requires a different), and sandboxing (flatpak has no access to the (file)system unless specified).
How about you use the native packages then?
Sometimes I do pull the source and build natives myself, just to spite these fuckers
But that’s only because I know how to fix their seventeen build errors
Meanwhile I’m chilling with the AUR and a rather good knowledge about how to create and maintain PKGBUILDs
well, users of atomic distros that can’t do that and have to rely on containerized applications e.g. via flatpak (appimage, … that other one …)
No they don’t. You can always install them in a distrobox, or layer them, or just copy them into your home. It’s Linux, you’re free to choose which way you like.
That one meme, with the kid sticking a stick into their own bicycles’ wheel
Temba, their hands open.
Not up to date enough / unavailable / I don’t want to compile. Spin the wheel, pick a reason.
Lol nvidia
Just get rid of everything Nvidia. Problem solved.
Aren’t those packages alternate Proton or GE-Proton versions that were installed via ProtonUp-QT?
I run an all AMD system and I still get those updates.
