https://fedoraproject.org/wiki/Changes/SwitchToDnf5
The DNF5 change proposal states that:
Tools that modify system software, such as PackageKit, may exhibit different behavior when used alongside dnf5 to manage the same system, as previously described. Additionally, it is strongly recommended to consider porting to the dnf5 API in this context.
Tools that modify system software, such as PackageKit, may exhibit different behavior when used alongside dnf5 to manage the same system, as previously described.
Additionally, it is strongly recommended to consider porting to the dnf5 API in this context.
Also,
Though the RPM DB, which contains the database of installed packages, remains the singular source in the system, the transactional history and installed packages reasons in dnf and dnf5 is not shared, and they now use different formats. Transactions performed in dnf will not be visible in dnf5, and vice versa. Therefore, when concurrently using dnf and dnf5 on the system, packages installed by one of them as dependencies will appear as user-installed to the other one, potentially leading to them not being auto-removed later.
Though the RPM DB, which contains the database of installed packages, remains the singular source in the system, the transactional history and installed packages reasons in dnf and dnf5 is not shared, and they now use different formats.
Transactions performed in dnf will not be visible in dnf5, and vice versa. Therefore, when concurrently using dnf and dnf5 on the system, packages installed by one of them as dependencies will appear as user-installed to the other one, potentially leading to them not being auto-removed later.
which is very sad considering that i just fixed sharing the history between dnf4 and packagekit...
I also remember that at some point the document discouraged the concurrent use of dnf4/packagekit and dnf5, but that seems to be gone now.
In any case, we should try to avoid having Discover be the only remaining user of PackageKit, if/when GNOME Software switches to using the dnf5 daemon.
It is quite sad that dnf5 is redefining a dbus interface very similar to PackageKit, rather than implementing the exact PackageKit interface...
But rather than writing a DNF5 backend for Discover, I'm envisioning a PackageKit backend that forwards the dbus calls to the DNF5 daemon, exploiting the similarity between the two interfaces.
Some links from another discussion: - WIP support in GNOME Software: https://gitlab.gnome.org/mcrha/gnome-software/-/tree/wip/dnf5daemon/plugins/dnf5?ref_type=heads - https://dnf5.readthedocs.io/en/latest/tutorial/install-build-deps.html - https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5#Scope - https://dnf5.readthedocs.io/en/latest/dnf_daemon/index.html
CC @mcrha
The DNF daemon is very immature, but it should not be too difficult to port the dnf backend in PackageKit to libdnf5.
Metadata Update from @timaeos: - Issue tagged with: need-work
Log in to comment on this ticket.