Red Hat developers are proposing to eventually replace YUM with DNF, a fork of Fedora’s default package manager, in F22. DNF is a fork of the YUM package manager being developed full time by Ales Kozumplík and Radek Holý, with contributions from Yum expert Zdeněk Pavlas and university student Jan Šilhan.
Developers forked YUM in January 2012 so that they could work on overhauling ‘YUM’ and fix the problems outdated YUM was facing, DNF has been available in repositories since Fedora 18.
How does it affect average user?
There won’t be any visible change for GUI (graphical user interface) as DNF will silently work in the back-ground. Those who use command line won’t see any difference either as there are no or ‘minimal’ changes to the command syntax, ofcourse, one may have to use dnf insted of yum when running commands like ‘dnf update’.
Those who want to test dnf can install it dnf from repositories and try performing operating using dnf instead of yum.
Why dnf and not Yum?
According to Kozumplik, the dependency solver employed by YUM is outdated and there are a lot of better solvers out there. To that end, DNF uses SUSE’s libsolv, with hawkey as a C and Python wrapper. Libsolv, he adds, “employs a very solid algorithm to do the resolving.”
Then there are many other issues with aging YUM, Kozumplik explained them very well in his story done by Bruce Byfield.
What is YUM?
YUM or Yellowdog Updater, Modified, is the default software package manager that installs, updates, and removes packages on RPM-based systems. It automatically computes dependencies and figures out what things should occur to install packages. So replacing this with a new package manager was a huge decision. But the open source package manager had some flaws that have been proving to be counterproductive and which basically made the transition to the new manager an essential decision.