Changes/ReplaceYumWithDNF

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
(Created page with "<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = ...")
 
Line 31: Line 31:
 
DNF was forked from Yum in January 2012 and available for experimenting in fedora since [https://fedoraproject.org/wiki/Features/DNF release 18]. The project is now fully capable of replacing Yum in new Fedora installations. We want DNF to become the new default packaging tool in Fedora 22. This entails:
 
DNF was forked from Yum in January 2012 and available for experimenting in fedora since [https://fedoraproject.org/wiki/Features/DNF release 18]. The project is now fully capable of replacing Yum in new Fedora installations. We want DNF to become the new default packaging tool in Fedora 22. This entails:
  
* letting system administrators (including users who routinely manage their packages using the legacy Yum) perform all common packaging operations using DNF, with no or [http://akozumpl.github.io/dnf/cli_vs_yum.html minimal and documented] change to the command syntax. (done)
+
* letting system administrators (including users who routinely manage their packages using the legacy Yum) perform all common packaging operations using DNF, with no or [http://akozumpl.github.io/dnf/cli_vs_yum.html minimal and documented] change to the command syntax, apart from replacing the command name. (done)
 
* providing implementation of Anaconda backend so system can be bootstrapped completely without using legacy Yum. (done)
 
* providing implementation of Anaconda backend so system can be bootstrapped completely without using legacy Yum. (done)
 
* providing alternative to all Yum plugins from yum-utils (ongoing)
 
* providing alternative to all Yum plugins from yum-utils (ongoing)
* providing alternative to all release engineering tools (repoquery etc.) from yum-utils (ongoing)
+
* providing alternative to all release engineering tools (repoquery, bodhi etc.) from yum-utils (ongoing)
 
* being ready/having the capacity to help out users with migration of their custom legacy plugins and extensions to DNF. The solid [http://akozumpl.github.io/dnf/api.html API documentation] we provide is of great advantage here. (ongoing)
 
* being ready/having the capacity to help out users with migration of their custom legacy plugins and extensions to DNF. The solid [http://akozumpl.github.io/dnf/api.html API documentation] we provide is of great advantage here. (ongoing)
  
Line 61: Line 61:
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
  
In F22 we will release DNF as dnf-1.0.0, providing yum-4.0.0 and obsoleting yum < 4.0.0. Doing F21->F22 upgrade should thus transparently replace the legacy Yum with DNF/Yum4.
+
In F22 we will release DNF as dnf-1.0.0. Yum will still be installable alongside DNF.
  
Users will still have the possibility to manually remove DNF and install the (legacy) 'yum' package.
+
Users will have the possibility to manually remove DNF only use the (legacy) yum package.
  
 
For the set of incompatible CLI calls see [http://akozumpl.github.io/dnf/cli_vs_yum.html DNF documentation].
 
For the set of incompatible CLI calls see [http://akozumpl.github.io/dnf/cli_vs_yum.html DNF documentation].
Line 69: Line 69:
 
== How To Test ==
 
== How To Test ==
  
Install dnf/Yum4 and carry out your usual packaging operations.
+
Install dnf and carry out your usual packaging operations using the <code>dnf</code> command, for instance:
 +
 
 +
  dnf upgrade
  
 
== User Experience ==
 
== User Experience ==
Line 77: Line 79:
 
== Dependencies ==
 
== Dependencies ==
 
* The main depending package is Anaconda and we've ported it to use DNF as a backend.
 
* The main depending package is Anaconda and we've ported it to use DNF as a backend.
* Plugins. Core plugins will be ported, we will provide help with porting users' custom legacy plugins.
+
* Plugins. Core plugins are/will be ported, we will provide help with porting users' custom legacy plugins.
 +
* Release engineering tools. Work on porting the tools is ongoing.
  
 
== Contingency Plan ==
 
== Contingency Plan ==
* contingency plan: stay with Yum, release DNF as Yum4 but do not obsolete the legacy Yum. This way both projects can be installed together, <code>/usr/bin/yum</code> pointing to the legacy Yum in this case.
+
* contingency plan: stay with Yum, release DNF 1.0 but keep Anaconda installing through Yum and do not make announcement/recommendation to users to switch to DNF.
 
* contingency deadline: beta freeze.
 
* contingency deadline: beta freeze.
* as long as Anaconda installation, all CLI operations from Yum and the most critical plugins work, this change can ship.
+
* as long as Anaconda installation through DNF, all CLI operations and the most critical plugins work, this change can ship.
  
 
== Documentation ==
 
== Documentation ==

Revision as of 08:50, 6 March 2014


Contents

Replace Yum With DNF

Summary

Make DNF/Yum4 the new default packaging tool in F22.

Owner

Current status

  • Targeted release: Fedora 22
  • Last updated: (DATE)
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

DNF was forked from Yum in January 2012 and available for experimenting in fedora since release 18. The project is now fully capable of replacing Yum in new Fedora installations. We want DNF to become the new default packaging tool in Fedora 22. This entails:

  • letting system administrators (including users who routinely manage their packages using the legacy Yum) perform all common packaging operations using DNF, with no or minimal and documented change to the command syntax, apart from replacing the command name. (done)
  • providing implementation of Anaconda backend so system can be bootstrapped completely without using legacy Yum. (done)
  • providing alternative to all Yum plugins from yum-utils (ongoing)
  • providing alternative to all release engineering tools (repoquery, bodhi etc.) from yum-utils (ongoing)
  • being ready/having the capacity to help out users with migration of their custom legacy plugins and extensions to DNF. The solid API documentation we provide is of great advantage here. (ongoing)

Benefit to Fedora

  • A CLI package manager tool built on modern depsolving technology allowing for faster and less memory-intensive operation.
  • Documented, solid Python API.
  • C bindings for lower level libraries:
    • hawkey for package querying and depsolving. PackageKit is already making use of hawkey.
    • librepo for repo operations. PackageKit is already making use of librepo.
    • libcomps for comps operations).
  • Unlike Yum, DNF runs in both Python 2 and Python 3.

Scope

This change will be completely transparent for users that use only the graphical package management tools. For anybody using the command line directly there will be some differences, but all the important operations are available with DNF, using the same CLI syntax.

  • Proposal owners: The majority of tasks on this change are completed. Some plugins and API calls still need to be added. The Anaconda payload implementation needs more testing, Fedora Test Day for this is pending.
  • Other developers: We provide the paylaod implementation for Anaconda developers. Developers of other extensions and developers of plugins that are not part of yum-utils will have to update their code.
  • Release engineering: Release engineering tools that are internal to the releng teams and not part of yum-utils will need modifications to migrate to the DNF API.
  • Policies and guidelines: None at the moement.

Upgrade/compatibility impact

In F22 we will release DNF as dnf-1.0.0. Yum will still be installable alongside DNF.

Users will have the possibility to manually remove DNF only use the (legacy) yum package.

For the set of incompatible CLI calls see DNF documentation.

How To Test

Install dnf and carry out your usual packaging operations using the dnf command, for instance:

 dnf upgrade

User Experience

See above.

Dependencies

  • The main depending package is Anaconda and we've ported it to use DNF as a backend.
  • Plugins. Core plugins are/will be ported, we will provide help with porting users' custom legacy plugins.
  • Release engineering tools. Work on porting the tools is ongoing.

Contingency Plan

  • contingency plan: stay with Yum, release DNF 1.0 but keep Anaconda installing through Yum and do not make announcement/recommendation to users to switch to DNF.
  • contingency deadline: beta freeze.
  • as long as Anaconda installation through DNF, all CLI operations and the most critical plugins work, this change can ship.

Documentation

DNF Documentation Site, the package ships manual pages of course.

Release Notes