Fedora is a meticulously polished distribution in every aspect, rightfully earning its place among the top Linux ones. However, its Achillesโ heel is the package manager it employs, which feels outdated by todayโs standards.
Its usage can test a userโs patience, as its performance lags notably behind Debianโs speedy APT. And comparing it to the swift efficiency of Archโs Pacman is, frankly, not even a fair contest. However, this could all change in Fedora 41.
The Proposal
The Fedora Project has announced a proposal to switch its default package manager from DNF to DNF5 in the upcoming Fedora 41, expected for release around mid-October.
Spearheaded by Jan Kolarik and Jaroslav Mracek of Red Hat, this proposed change is currently under public review and awaits approval from the Fedora Engineering Steering Committee (FESCo).
DNF5: Features and Improvements
DNF5 promises significant improvements over the current version. It aims to enhance the user experience by offering faster query processing and a reduced footprint.
This means it will not require Python dependencies and will help eliminate metadata redundancy by sharing metadata between dnf5 and the new dnf5daemon. Here are the main benefits to expect.
- Enhanced Performance: DNF5 promises faster repository metadata processing and improved package query operations, aiming to save users precious seconds during package management tasks.
- Reduced System Footprint: By eliminating Python dependencies and merging the functionalities of DNF and MicroDNF, DNF5 offers a significantly smaller installation size, reducing metadata redundancy.
- Unified Experience: Fedora aims to provide a consistent package management experience across all platforms, with DNF5 serving as the sole package manager for servers, workstations, and containers.
Looking Ahead
The DNF team has outlined a meticulous plan for those concerned about the transition to ensure a smooth upgrade path. Upon system upgrade or DNF5 installation, the DNF5 package will automatically replace the existing DNF package.
Moreover, backward compatibility for the yum command and a new daemonized service, dnf5daemon, are included to maintain a seamless user experience.
However, for all this to happen, the Fedora Engineering Steering Committee (FESCo) must first approve the proposal before it can become a reality. Currently, it is in its second iteration, following extensive community feedback gathered from its initial attempt.
To wrap up, itโs worth noting that discussions about DNF5 taking over as the default package manager began around a year and a half ago to introduce it in Fedora 39.
Clearly, that transition didnโt take place, and even the upcoming Fedora 40 release, slated for next month, has avoided implementing this significant change.
Nevertheless, there’s a strong sense of optimism that the proposal for DNF5 this time will be green-lighted, paving the way for its anticipated debut in Fedora 41. The proposalโs entire content can be seen here.
