3 ms·
AppImage is one solution too.
by TheChaplain 4y ago
AppImage is one solution too.
- mardifoufs 4y agoAppimage isn't truly portable, it still usually depends on specific versions of glibc (and other dependencies that it assumes come with the host OS).
- edflsafoiewq 4y agoAn AppImage is bascially a zip file that extracts itself and then runs a binary in the extracted dir. It's still up to you to make sure the binary inside the AppImage is actually portable.
- isr 4y ago(you probably know this and were simplifying, but for the benefit of others who may not ...) Its a filesystem, not an archive. So its contents aren't extracted anywhere on your drives. It stays within the appimage. The squashfs fs used is optimised for use as a read-only, fast access fs. Entire distro's have been built and used (for over a decade), where everything is contained in 1 or more overlaying squashfs containers. Its close to the most optimal method of distributing AND ACCESSING read-only stuff. All the appimage does is it mounts its internal squashfs, and the runs its internal AppDir program (appimages are essentially "squashed" appdirs) Appdirs themselves are a sadly underrated agnostic pkg'ing format, which have great flexibility & utility (imho).