Sergei von Alis

I believe this could be fixed on the Steam flatpak app side and doesn't really have much to do with flatpak-builder.

> How is this related to the Steam flatpak? I don't see anything that could change there It's possible add each extension's `share` subdir to `XDG_DATA_DIRS` in the app wrapper....

Any update on this? I totally agree with @pulb saying >this should be on top of the priority list - convenient features like this look like a very convincing selling...

As far as I understand, Flatpak isn't tied to flatpak-builder and it's completely possible to create ubuntu-based runtime (with debootstrap or so) and put ubuntu's packages into app budle built...

Well, maintaining such runtime doesn't look harder than maintaining a regular container for me. I we have a tool to automatically pull listed packages from a repository and install them,...

I think if we are just pulling binary packages from a repository, we only have to watch for ABI changes. It shouldn't be similar to maintaining a full-featured distribution fork....

>set up some automatic scripts to try to do this The whole issue is about such scripts, isn't it? I just say that installing binary packages into app/runtime should be...

The issue is still present with flatpak 1.6.2 and ostree 2019.4

I believe I've found the root cause. binutils (and gcc) autotools creates hardlinks on install, so that e.g. files `bin/i686-w64-mingw32-objdump` and `i686-w64-mingw32/bin/objdump` are the same file. While rofiles-fuse unconditionally denies...

@tinywrkb I believe this is unrelated, the original issue can't be fixed by changing permissions.