Another thing I see with appImage files is that if they need
configurations, they are stored in the location where I expect them to
be. In other words, I downloaded the subsurface appImage that they link
to from the website, made it executable, in this case by ticking the
execute checkbox under the permissions tab in the file's properties
window, but chmod will do just as well for that, then ran the file. I
got an accessible pop-up window right away asking if I wanted to keep
checking for updates every two weeks, and in spite of the fact that I
didn't even know how to use the application, it seems it just worked
fine and didn't break accessibility in any way. It does have a
configuration folder that it uses, and I can see that it stored it in
~/.subsurface, just as I expected. This has to be the best way for
developers to build their application for multiple distributions, and it
also has to be one of the easiest methods I've seen for downloading an
application direct from the author's website and just getting it running
without any hassle. I do have to wonder if the tools used for making
these appImages are available for ARM-based computers like my router, my
Odroid N2 and my Raspberry Pi. For now, this is what would make Flatpak
most attractive, since even though it has central package repositories,
Flatpaks can usually run on just about anything that has a packaged
version of the Flatpak system.
~Kyle
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/blinux-list