El jue, 08-10-2026 a las 11:51 +0200, Jelle van der Waa escribió: > What's the reasoning behind not using default alpm PackageKit > backend? > As you basically implemented your own now.
It's not just a rewrite of the PackageKit backend. The stock alpm backend refreshes pacman's own sync databases, which is an -Sy. Installing anything afterwards without upgrading is a partial upgrade, which Arch doesn't support (or at least doesn't usually handle very well). That's also why Arch builds GNOME Software without PackageKit (I suppose). alpm-dbus moves the Arch policy into a single system service: - it refreshes into a private database dir; - installing with updates pending is -Syu, never -Sy foo; - it follows the full pacman.conf, HoldPkg, and upgrades the keyring first; - it's the only privileged process, and each action is authorized through polkit. PackageKit is then just one client of it, through alpm-packagekit. Other frontends don't need PackageKit at all: the GNOME Software plugin (gsp-alpm) talks to the service directly, and a Discover backend could do the same. Greetings. -- Óscar García Amor | ogarcia at moire.org | http://ogarcia.me
signature.asc
Description: This is a digitally signed message part
