I've been working on a fork of GNOME Software focused on speed and fixing bugs. It now runs as a Flatpak, and unlike upstream's dev Flatpak, which only handles Flatpak apps, it can also manage the host:
rpm-ostree updates on Silverblue
.deb packages through PackageKit on Ubuntu
snaps through snapd
dnf5 and fwupd are built in, but less tested
It brings its own GNOME 51 runtime, so you get the new version on older distros without changing the system. On first start it asks whether to replace your system's Software in the background. That's optional and easy to undo.
The obvious catch is that it isn't really sandboxed. It reads the host's /usr and /etc, talks to system daemons like rpm-ostreed, PackageKit and snapd, and starts programs on the host. If it couldn't do that, it couldn't do its job.
The tricky part was rpm-ostree, and for that we borrowed the approach Ptyxis uses with ptyxis-agent: anything that needs the host runs on the host. rpm-ostreed creates a new socket in the host's /run for each transaction, and a Flatpak can't get at /run, so every update failed with "Could not connect: No such file or directory". We ship a small relay with the app (it only needs the C library) and start it on the host with flatpak-spawn --host. As with Ptyxis's agent, flatpak-spawn passes it one end of a socket pair. Plain pipes didn't work, because GDBus only offers EXTERNAL auth on a Unix socket and rpm-ostreed, running as root, accepts nothing else. So the relay sends the client's first byte with its own credentials, then just passes the data along. Software still speaks normal D-Bus over it, so progress, cancelling and daemon crash handling didn't change. We also build without librpm, libostree and librpm-ostree, since copies in the Flatpak would have to match each host's database versions and rpm-ostree needs its whole Rust toolchain. Instead the plugin runs the host's own tools: rpm-ostree db list for the deployment's packages (67 ms for 1505 packages on Silverblue 45), rpm -qf for file owners and rpm -qp for .rpm headers.
flatpak install --user https://gnome-software-next-855abc.pages.gitlab.gnome.org/flatpak/org.gnome.Software.flatpakref
Source: https://gitlab.gnome.org/user_c1a5830a/gnome-software-next
Some honesty up front: the changes were written with generative AI, so please read them before installing something that manages your system. It's also only been tried on a few setups: mostly Silverblue 45 and an Ubuntu 26.04 VM. If it breaks on your system, I'd like to hear about it.
So, my actual question: do you think something like this could ever be accepted on Flathub, given how many permissions it needs? Or is an app that manages the host just the wrong fit, whoever maintains it? It also uses the same app ID as GNOME Software, so I assume that would have to change too. Curious what people here think.