[lmm]

> Well that input library is not an issue of the flatpak environment but an issue of the application and/or that library. That error could have easily occured if the application linked an old version of that library and the new version of the daemon was incompatible.

But that wouldn't happen in a distro-packages environment, because the distribution would ensure that everything was built against the same version of the library.

> This is an issue Linux created because everyone makes their own solution and then distro managers will silently patch over the mistakes, so it all kinda works together.

And flatpak is yet another case of that - doing their own incompatible thing instead of fixing what's there already.

[zaarn]

>But that wouldn't happen in a distro-packages environment, because the distribution would ensure that everything was built against the same version of the library.

This does not ensure that the library is compatible with the package, it only ensures that it builds.

>And flatpak is yet another case of that - doing their own incompatible thing instead of fixing what's there already.

They are working on standards that would improve things regardless of whether you're in a container or not. For example, the flatpak portals generally work just as well if you don't use flatpak at all, so apps don't care if they are inside our outside it.

This is part of the Freedesktop initiative on various things around Linux, which is already followed by quite a majority of desktop apps (and CLI apps), so there is a standard that improves things as they are.

Portals give you a standard way to interact with the user and the system that don't rely on distro specific patches.