A new category last year that had extremely close results.

--jeremy

For me, Flatpak is the only format that even functions. AppImage is useless to me (it doesn't install and integrate into the menu, so I have no desire to touch it), and Snap doesn't work if you have a /home directory anywhere but /home/<user>, which my domain users are /home/local/<domain>/<user> so I literally cannot use snaps. And the Snap team is aware of this limitations and said it's a very low priority to bother fixing.

1 members found this post helpful.

This is the only category where I would have selected a "None of the above". Call me a Luddite, but huge downloads, confusion caused to users who can't distinguish between universal packages and normally-installed packages, difficulty in supporting said packages, etc., they're not my favourite cup of tea. However, I can see why they came into being.

1 members found this post helpful.

AppImage. I use the Neovim AppImage, and I think AppImage is also the native format for itch.io's desktop client.

Snap is automatically disqualified (for me) because it requires systemd.

I warmly recommend to not use any of those since the Flatpak failure. No ticks from me.

Snap I found to be very straightforward to package new applications, AppImage very bothersome, and Flatpak very difficult (and works only for desktop apps, if I'm not mistaken)

1 members found this post helpful.

.tlz

Of course you CAN integrate AppImages into your system's menu: just run the (optional) 'appimaged' daemon. You can download it as an AppImage even, so you can easily get rid of it again (just delete that one, single, damn, f*cking file!) in case you should not like it: https://github.com/AppImage/AppImage...-i686.AppImage

ROSA:
Debian:
Ubuntu:
Archman (Arch):
No, I can't run that daemon, because it's not available to install it to get it to run. Not downloading random software from the internet to run as a root daemon, NO WAY. That smacks of Windows. I left Windows for a reason. If there were packages to install the appimaged then I'd consider giving them another try, but as it stands, there isn't any way to install the daemon properly that I can see.

So I stand by my original statement...it doesn't integrate into the menu.

The beauty of AppImage-d software is that you do not need to install it. They implements the "One App == One File" paradigm and just run (without requiring such a venerable concept as "installation").

It's not "random", it's one you'll actively select. It was packaged by the original authors of the software themselves. If you run that software after it was packaged by Debian, RedHat, Fedora, Ubuntu, SuSE or other distro packagers, you'll still also have to trust these same authors of the software.

No. No AppImage ever needs root to run it. All AppImages can be run without requiring extra privileges. The 'appimaged-x86_64.AppImage' daemon for integrating any other AppImage into the user's personal start menu also runs entirely in user space -- no special exception here.

It's only your own venerable, ancient pre-judices which merely are aware of...
(1) traditional packaging methods,
(2) daemons running only with root privileges...
....which prevent you to "see anything beyond the edge of your own plate".

I guess you do not expect me to be convinced by your arbitrary statements, just because they are proclaimed with utter personal conviction.
So I stand by my own statement: AppImages DO integrate into the menu -- if you just want them to.

1 members found this post helpful.