My issue with snap is how tightly integrated it must be with the entire OS, where flatpak can just be run in your user’s home context, without the need of running daemons and mounting virtual filesystems and all that.
That’s astonishing to me. Why?! I feel like Ubuntu really is shooting itself in the foot with this move.
Krita only offers official support for their AppImage builds, and I believe there’s good reason for that.
Apparently building as an AppImage allows for specific libraries to be bundled together. And it also simplifies support since every user is using the same libraries as everyone else.
It’s pretty much a Linux equivalent to Portable Executables bundled with their own DLLs on Windows. Although, it comes at the cost of a bloated filesize.
So this is supported in Flatpak, but it’s a bit more complicated than in AppImage. I support their decision to stick with AppImage, I honestly think it’s a really good solution, but it feels like it’s lacking a bit of polish around integration with a fully-featured desktop environment. DEs like Gnome and KDE should really have support for a $HOME/appimages directory, that you can drag+drop into like on OSX. These programs would then be in the path and could show up in the “start” menu (and their analogues)
Yeah, I had problems with getting shortcuts working in Gnome. I ended up making a custom .desktop file in ~/.local/share/applications/.
But even then it didn’t show up, so I had to enable the legacy “Applications” Gnome extension.
I’d love for AppImages to be better supported. Yes, they’re not sandboxed but holy hell they work well for obscure or older software. Linux, for as much as I adore it, handles “legacy” software sooo much worse than windows (at least pre win10).
There are a bunch of different ways to solve shared library issues (nix/flatpack/etc), but for things I know aren’t actively worked on and/or feature complete, a few MB of storage is well worth the lack of headaches elsewhere.
Maybe flatpacks are the answer (especially if Canonical or another big player joins up), but I generally don’t need things sandboxed for the sake of security - it’s not worth the extra headache elsewhere.
There is a (ironically?) really good flatpak for managing AppImages called GearLever, its basically drag and drop and it moves the appimage to a standardized directory and creates desktop files for you. It also can handle checking and auto-updating them if they are either hosted on github or otherwise have a searchable releases page. I started downloading more AppImages since discovering it, my main gripe was all the plumbing to get them on the desktop.
This can also be done with a standard binary by setting its rpath. Similar to how some Windows programs have a folder full of DLLs, you can tell the linker at compile time to have the binary look in its own directory (or a subdirectory, or any arbitrary directory) for libraries.
Maybe there’s some usefulness to amalgamating that all into a single file
I have tried setting both the rpath and LD_LIBRARY_PATH with my own programs, but there’s still a problem. Even though you can get the linker to load from your specified libraries, it can’t resolve symbols that have changed location.
Even though the functionality of libc and libstdc++ haven’t changed in years, symbols get changed every system update. And then the linker will complain that such-and-such library version is required, or that it wasn’t able to find some obscure function handle.
I also remember hearing Mr. Torvalds himself complain about it a while ago. Something about the GNU people always breaking userland code.
Maybe there’s some shell-script or helper application that can re-link an older executable to newer libraries at runtime, but I don’t know of one.
Every year or so I check in to see if Lunduke is still bananas.
Glad to see the trends are trending.
Companies might use opensource because its convenient for them. When it is no longer convenient for them they discard it or change the license. They do not and have never believed in the vision.
Are they evil (yes!), but they behave mostly opportunistically. So its no surprise seeing events unfold the way they have been. The real change happens at the fringes as others have said.
can’t you alias?
like, every install, just alias a bunch of the terri-bad things away in your profile / dotfiles?
like alias df='df -h -T -x tmpfs -x squashfs'
or some such?
I hear you on snaps though, they pushed me away from my beloved Ubuntu-Martin…