[SOLVED] Will 4MLinux ever support AppImages, Flatpaks, & Snaps?
4MLinuxThis forum is for the discussion of 4MLinux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Appimages and the like are not supposed to need system support, but be self contained. That's the whole point of them. People only bother when the dependencies are horrendous, or next to impossible to find/compile.
That said, some guys compile these on, for example a RH system, test them on a RH system, and release them. They the barf big time on something like Arch or Slackware, which is set up differently, uses different lib versions, etc.
Let’s take AppImages as an example (they are the simplest). The idea behind them is that they should work under any Linux distro. Download an image, make it executable (chmod 755), double click on it, and your program should be opened. No matter what distro you are using.
The problem is that AppImages expect that your distro includes a wide set of various libraries that are present in mainstream distributions like Debian. If a library is missing, your program will not start.
If I start to add new libraries (one by one) required by AppImages, my 4MLinux will soon became a new (fat) Debian. But, as you know, my idea is to maintain a small, extremely fast distro with a well defined limited set of features.
Let’s take AppImages as an example (they are the simplest). The idea behind them is that they should work under any Linux distro. Download an image, make it executable (chmod 755), double click on it, and your program should be opened. No matter what distro you are using.
The problem is that AppImages expect that your distro includes a wide set of various libraries that are present in mainstream distributions like Debian. If a library is missing, your program will not start.
If I start to add new libraries (one by one) required by AppImages, my 4MLinux will soon became a new (fat) Debian. But, as you know, my idea is to maintain a small, extremely fast distro with a well defined limited set of features.
I don't think you need be slave to the small/light concept these days.
In the past, small, light software actually made a huge difference, but not now, even with a weak & gutless PC (pretty much like mine). I have firefox,palemoon libreoffice & a library program open, and me memory usage is 1.25G. Run a sensible Window manager, don't install junk, but you needn't fuss about libs imho. Even opening 860Megs of AppImages only increased the memory footprint by 200Megs, showing that linux has efficient memory usage. My last box was an AMD twin Turion Northbridge/Southbridge thing with 4 Gigs. One Gig died, which reduced it to 3. But it still ran fine.
If you're running a single arm7 core and 1G, then maybe. But most pcs breeze through what older pcs struggled to do.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.