Fedora 39 seeks to use DNF5 by default for better performance and improved user experience


With Fedora 39 next spring, it will likely replace DNF, libdnf, and dnf-automatic with the new DNF5 packaging tool and libdnf5 support library. DNF5 should improve user experience and provide better performance to handle software management on Fedora Linux.

The change proposal still needs to be approved by Fedora’s Engineering and Steering Committee (FESCo), but given Red Hat’s involvement with DNF(5), it will likely be accepted and hopefully all will be fine. completed in time for completion during Fedora Cycle 39. The change proposal summarizes things as follows:

The new DNF5 will bring a significant improvement in user experience and performance. The replacement is the second stage of the Fedora Software Management stack upgrade. Without the change, there will be several software management tools (DNF5, old Microdnf, PackageKit and DNF) based on different libraries (libdnf, libdnf5), offering different behavior and not sharing history. We can also expect DNF to have limited support from upstream. The development of DNF5 was announced on the Fedora-Devel list in 2020.

DNF5 removes Python code to produce a smaller system, faster performance, and to replace existing DNF and microdnf tools. DNF5 also unifies the behavior of the software management stack, introduces a new daemon as an alternative to PackageKit for RPMs, and should perform much better. Faster performance can be expected for querying repositories, hinting operations, RPM queries, and metadata sharing.

Those interested in learning more about the tentative plans for DNF5 in Fedora 39 can see the proposed change on the Fedora Wiki as an exciting innovation to look forward to in 2023.


About Author

Comments are closed.