3 ms·
> it's something you get for free with shared dependencies. Yes, it's also something you get for free with Flatpaks; if the base image gets updated, the Flatpa
by esarbe 5y ago
> it's something you get for free with shared dependencies.
Yes, it's also something you get for free with Flatpaks; if the base image gets updated, the Flatpaks running on it will also get fixed libraries without having to rebuild the Flatpak.
From that point of view, there's not actually that much difference between an RPM or DEB and .flatpak; you have a base system along with some dependencies that will get updated and you'll get the updates 'for free'. Everything that is not included in the base image you will have to provide yourself and you'll have to do it yourself.
- necovek 5y agoI think we are arguing past each other :) Technically, you can package all your dependencies into a .deb or .rpm file too. But that'd not what's usually done, just like you don't ask for your dep to be included in the base image, but bundle it yourself. This is just a workaround to stop from having to include all the same deps a gazzillion times.
- esarbe 5y ago> I think we are arguing past each other :) You might be right there. :D I just remembered that "base image" in Flatpak lingo is a "runtime."