[HEADS UP] Update your Qt application with access to KDE/Gnome configuration

Aleix Pol aleixpol at kde.org
Fri Oct 5 18:33:59 UTC 2018


On Fri, Oct 5, 2018 at 4:58 PM Alexander Larsson <alexl at redhat.com> wrote:
>
> On Fri, Oct 5, 2018 at 4:12 PM Aleix Pol <aleixpol at kde.org> wrote:
> >
> > On Fri, Oct 5, 2018 at 1:15 PM Jan Grulich <jgrulich at redhat.com> wrote:
> > >
> > Another possibility would be to find a way for flatpak-builder to
> > detect that these arguments are missing.
> > I don't think it's great that we give the possibility to have
> > applications broken in unknown ways and push developers to always have
> > to copy&paste certain parts if they don't want some integrations just
> > not to work.
>
> For the gtk+ side the long term solution we plan is to have a
> sandbox-specific implementation gsettings backend that would work via
> a proxy. This way apps would work (and have access to their own
> configuration only instead of everything) automatically once we put
> the backend in the runtime.
>
> Could kde have a similar solution?
>
> Of course, this needs work and its possible that we would want better
> temporary fixes until such work is done.
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>  Alexander Larsson                                Red Hat, Inc
>        alexl at redhat.com         alexander.larsson at gmail.com

We could look into it, but it's not just the settings, there's other
things. Environment variables, dbus paths, etc.
https://phabricator.kde.org/source/flatpak-kde-runtime/browse/master/org.kde.Sdk.json$62

Aleix


More information about the Flatpak mailing list