I use Flatpaks mostly because I like having my base os and gui minimal as possible. Every thinking that is not core os I install as a flatpak. This is great because I didn’t have to install dependencies like lib32 and other libraries on my root partition. Lean and mean.
It’s like a separate package manager with much less granularity than most distros packages. It’s a very clever implementation that has got its pros and cons, but massive duplication of libraries isn’t one of them.
I use Flatpaks mostly because I like having my base os and gui minimal as possible. Every thinking that is not core os I install as a flatpak. This is great because I didn’t have to install dependencies like lib32 and other libraries on my root partition. Lean and mean.
But doesnt each flatpak is packed with its own dependencies? So bascially you have the same dependency over and over.
No, each runtime is only used once. You only get duplicates for apps that use different runtimes or for dependencies that are bundled in the app.
Isn’t flatpaks exactly this?
No, it’s a layered model like Docker. They depend on various images that can be shared across applications targeting the same runtime.
Didn’t know that, intresting, thank you.
It’s like a separate package manager with much less granularity than most distros packages. It’s a very clever implementation that has got its pros and cons, but massive duplication of libraries isn’t one of them.
You may be thinking of AppImage. That’s one file that contains everything.