Snap, Flatpak and/or AppImages?
Linux for blind general discussion
blinux-list at redhat.com
Sat Mar 5 17:38:51 UTC 2022
I understand this, not all package managers have all packages you may need, I know this, Ubuntu 20.04 LTS does not have BRLTTY above 6.3, which doesn't support my display, that's why I cannot run Ubuntu.
This is where AppImages, Snap and Flatpak can really make a difference, and it already does.
Please note, I used BRLTTY and Ubuntu as an example.
Sent from my MacBook Air
Phone: +27 (0)60 525 9181 <tel://+27605259181>
Email: brandt.steenkamp at gmail.com <mailto:brandt.steenkamp at gmail.com>
Twitter: @brandtsteenkamp <http://www.twitter.com/brandtsteenkamp>
> On 05 Mar 2022, at 17:00, Linux for blind general discussion <blinux-list at redhat.com> wrote:
> Images are generally used for new installation or live boot such as for repair disks. Package managers are best to add, remove, or update an already installed system. I think whoever started this thread doesn't understand that you need to use the correct tool for the job you are trying to accomplish.
> If your already installed system doesn't have an editor or a game you want to use, then the package manager allows you to add it. Redhat uses the 'rpm' package manager, and other distributions choose different tools.
> On 3/4/2022 5:08 PM, Linux for blind general discussion wrote:
>> So it does seem then like appImages are the way to go. It sounds like we get the absolute best of every possible scenario in this seemingly antiquated but actually highly innovative portable app technology. Why oh why do we have people saying that flatpak is the future, or worse, snapd is the future, when we have appImages that are highly portable, and can even be sandboxed in much the same way, but are much more versatile owing to the portability? It's really nice to be able to put all the appImages I need on a USB drive and just use them on any Linux computer. I guess the one drawback I can see is the update problem, where most don't update themselves, but having repositories and appImage managers available would seem to resolve that issue, also in a highly portable way.
>> Blinux-list mailing list
>> Blinux-list at redhat.com
> Blinux-list mailing list
> Blinux-list at redhat.com
More information about the Blinux-list