85
Flatpack, appimage, snaps..
(leminal.space)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Dec 2023
85 points (90.5% liked)
Linux
48376 readers
1095 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Software deployment that tackles dependency hell in a secure fashion while providing repeatable, atomic updates and rollback.
AppImage doesn't even provide a proper update system.
Can you elaborate on update system? AppImage is just a format, right? Whereas flatpak is a format and an entire toolkit for downloading and running flatpaks.
You already said it. Flatpak and Snap both include an entire system around updates and rollback which provide some pretty strong guarantees for update success. AppImage does not. It's got some libs available that an individual developer could use to implement their own update mechanism but isn't a built-in. And besides, without a system-level component that manages install/update/rollback, you can't have any guarantees about the update process. You're back to the Windows-world per-app
update.exeparadigm (orupdate.shin Linux).There's software for that. Honestly, i prefer that over the 'whole package or nothing' approach in Flatpack, which still has ~/.var for packages hardcoded btw.