On Tue, Aug 9, 2022, 16:31 Ben Koenig <[email protected]> wrote:
> ------- Original Message ------- > On Tuesday, August 9th, 2022 at 9:50 AM, John Jason Jordan <[email protected]> > wrote: > > > > On Tue, 9 Aug 2022 07:58:57 -0700 > > Vince Winter [email protected] dijo: > > > > > The way snap works is snaps apps are self contained images that > > > include all the libraries the app needs to run. So it doesn't have to > > > worry about dependencies being out of date in exchange for larger size > > > foot print on the system. > > > > > > How is this different from Appimages? What is the point of mounting > > them, why do they have to be mounted? I have several Appimages and they > > all run without needing to be mounted. > > AppImage is an application, and all of it's dependencies compiled into a > single executable file. If your distro provides a minimal set of shared > libraries, the AppImage can be executed since any specific library > requirements are included in the AppImage. However, the AppImage still runs > like any other program and reads/writes files to your home directly just as > you would expect. > . > https://docs.appimage.org/introduction/software-overview.html AppImage mounts its dependencies as overlay using fuse. It is different kind of animal than snap, but speaking of mount ... It does mount stuff too. In fact there is a lot of how-to's about how to deal with ApImage mount failures. Like this one: https://docs.appimage.org/user-guide/troubleshooting/fuse.html
