Linux

48328 readers

659 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Flatpack, appimage, snaps.. (leminal.space)

submitted 11 months ago by Squid@leminal.space to c/linux@lemmy.ml

61 comments fedilink hide all child comments

Appimage for me ticks all the boxes for cross distro package as its very portable, simple to run, what are devs trying to do when creating snaps and flatpack?

you are viewing a single comment's thread
view the rest of the comments

[–] rutrum@lm.paradisus.day 12 points 11 months ago (1 children)

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.

[–] avidamoeba@lemmy.ca 43 points 11 months ago* (last edited 11 months ago)

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.exe paradigm (or update.sh in Linux).