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 fork-bomb your computer.
They do? I've always seen that as being up to distro maintainers, and out of control of the devs.
And this, this is why I love the AUR
I think no one said it needs to be ON a distro's repos. That's a straw man.
A package should be available in a native package format in a way that doesn't cause conflict with what's in the official repo. The reasons for a single source of truth on installed status should be obvious; but given the format of some packaging and the signed assurance of provenance, thr advantages to a native format can be leaves ahead of even that.
Wow, is this meme a really naive take that is contradicted by - oh god, everything. Can someone know about enterprise Linux and also be this naive?
People always forget about appimages.
Your security people have not forgotten about appimages. It fills their nightmares.
Same app in native format: 2MB. As a flatpak: 15MB. As an appimage: 350MB.
Appimages are awesome, rock solid, and I have a few on my system, but flatpak never gave me any problem and integrates better with my KDE, and is smaller. Both have their advantages tho. I'm fine with using both. If you are a developer, make a flatpak or an appimage i dont really care just make your software available for linux. Both are fine, choose the one that fits your specific app the most.
But I also think appimages deserve the same attention and great integration with the OS as flatpaks. Stuff like that AppImageLauncher functionalities should just be integrated inside the DE itself.
But we need an universal package format for linux asap. Flatpak is on the front in this race, and I'm fine with it. Appimages second, for sure.
If you don't run your install off a 12 zetabyte NAS are you even a real linux user?
As they should /s
Honestly its neat but I don't see why I would want it over flatpak ever
I'm new to Linux. Every time I've had a major issue with an application it turned out to be due to a flatpak. I'll stick with other options for the time being.
Also at least let me compile it myself if not in a repo 😩
Nix: you package it yourself and do a pull request
Sadly, many flatpaks don't even work on NixOS properly because of assumptions about the file structure or similar
I'm a Debian fan, and even I think it's absolutely preferable that app developers publish a Flatpak over the mildly janky mess of adding a new APT source. (It used to be simple and beautiful, just stick a new file in APT sources. Now Debian insists we add the GPG keys manually. Like cavemen.)
And then change where we put them.
I know nothing about how flatpak works other than that it's containerized. But this meme tells me it's the OS's responsibility to create the flatpak, and not the developer's? Is that right?
No the most common way is for devs to package their own software as a flatpak since you can typically choose your preferred packaging tool to use inside of the flatpak.
Traditional package management typically is done by the distro maintainers.
Oh I see, I've got it backwards.