- 1 Summary
- 2 Owner
- 3 Resources
- 4 Current status
- 5 Detailed Description
- 6 Why it would be good for Mageia to do it
- 7 Test case
- 8 Tasks
- 9 Software / Packages Dependencies
- 10 What could disrupt development of this new feature
- 11 Planning
- 12 Contingency
- 13 Release Notes
- 14 Documentation
- 15 Packager comments
Switch to DNF as the default package manager.
- Name: Neal Gompa
- Email: firstname.lastname@example.org
This will require efforts by packagers and developers to remove perl-URPM and urpmi from the software stack.
- Targeted release: Mageia 7
- Last updated: 2017/09/16
- Percentage of completion: 0%
With the successful integration of DNF in Mageia 6, I would like to make DNF the main package manager for Mageia 7.
Why it would be good for Mageia to do it
Using DNF will allow us to leverage a more advanced software management stack supported by the upstream rpm.org project.
As mentioned in the Mageia 6 feature, DNF is actively maintained as part of the rpm.org project, meaning that it receives fixes and features as soon as RPM itself has it. With DNF, Mageia has a dependency resolver sharing common technology with Fedora and openSUSE, which has opened many opportunities to collaborate with them and benefit from shared efforts.
To be determined...
- Requires the completion of the following features
- Complete the implementation of the dnf-URPM CLI wrapper tools for urpmi CLI compatibility
Software / Packages Dependencies
Nothing additional beyond what is done for the dependent features.
What could disrupt development of this new feature
If not all of the dependent features can be completed in time, this feature cannot be implemented.
The dependent features need to be approved and worked on to make this feature possible.
If this fails to be ready for Mageia 7, then we continue with what we have and try again for Mageia 8.
The release notes should indicate that Mageia now uses DNF for its package management exclusively.