Alexander Larsson

@cgwalters I don't think we've proposed that before no, as it would be crazy. But with trust being in the dump file it seems less crazy, and this would potentially...

overall lgtm, with the above comments.

I think this if fine to merge as is, it just needs the conflicts resolved.

It seems like a useful end-user feature. But kludging up the lowlevel implementation by introducing "apps" that are not "apps" sounds like a horrible thing that will leak out all...

I.e. something that gnome-software could understand as " users may like " and do a nice UI for.

A proper solution could be done at the level of flatpak/libflatpak, and it would involve some new object instead of (mis)using a ref.

There is no real way we can check this. Any random user could use a runtime in a per-user install. We can't scan all homedirectories, not to mention the security...

I mean, we *could* check it against your per-user apps, but it will not help a multi-user setup, or the case when root runs the uninstall.

Also, the check would have to handle the case where the user install also has the runtime installed, because then its safe to uninstall the system one.

This is a tricky area. Bluechi is useful without QM, so we can't require the QM selinux policy to use it. On the other hand, the QM package is not...