Existing apps like GNOME Web (Epiphany) get away with this because the
files they are exposing are below $XDG_CONFIG_HOME, $XDG_DATA_HOME or
$XDG_CACHE_HOME, which take values below ~/.var/app, but the same is
not necessarily going to be true for apps like Steam that use --persist.
Preparatory work for supporting https://github.com/flatpak/flatpak/pull/4018
flatpak-spawn: Factor out path_to_handle()
This will let us deal with arguments that are a single path, instead of a GStrv of paths.
flatpak-spawn: Try to normalize exposed paths to be in ~/.var/app
The Flatpak portal will reject paths that do not resolve to the same thing in the container and on the host system. For example,
will not work, even if
would.
Existing apps like GNOME Web (Epiphany) get away with this because the files they are exposing are below $XDG_CONFIG_HOME, $XDG_DATA_HOME or $XDG_CACHE_HOME, which take values below ~/.var/app, but the same is not necessarily going to be true for apps like Steam that use --persist.