Revision as of 14:08, 31 May 2012

DNF, a new Package Manager

A preview of the next-generation Yum package manager, using hawkey/libsolv for backend.

People are asking why we didn't choose to adopt zif instead of fixing yum. The reasons are:

dnf looks for a middle ground between a sane API and some backwards compatibility.
dnf and hawkey are first steps toward using the same resolver accross the entire stack.
Libsolv is a well tested and proven code base, currently the most sophisticated and optimized dependency solving implementation.

@@ Line 7: / Line 7: @@
 == Summary ==
+A preview of the next-generation Yum package manager, using hawkey/libsolv for backend.
 == Owner ==
 * Name: [[User:akozumpl| Aleš Kozumplík]]
 * Email: akozumpl@redhat.com
@@ Line 16: / Line 17: @@
 * Targeted release: [[Releases/18 | Fedora 18 ]]
 * Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
-* Percentage of completion: 5%
+* Percentage of completion: 40%
 <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
@@ Line 25: / Line 26: @@
 People are asking why we didn't choose to adopt zif instead of fixing yum. The reasons are:
 * dnf looks for a middle ground between a sane API and some backwards compatibility.
-* we ultimately want unified resolver across the stack and dnf and hawkey is the first step towards that.
+* dnf and hawkey are first steps toward using the same resolver accross the entire stack.
-* using libsolv allows us to get closer to what SUSE uses. So it makes the RPM world easier to deal with.
 * Libsolv is a well tested and proven code base, currently the most sophisticated and optimized dependency solving implementation.