- 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 Associated Bugs
- 16 Packager comments
Port the installer to use DNF.
- Name: Neal Gompa
- Email: email@example.com
This will require efforts by the installer developers to port the installer to DNF.
- Targeted release: Mageia 7
- Last updated: 2017/09/16
- Percentage of completion: 0%
Our installer currently uses perl-URPM to do dependency resolution and package installation. In Mageia 6, we introduced DNF as a package manager. For Mageia 7, we want to have the installer ported to use the DNF package management engine. This will be done by using libdnf, the underlying C library that powers DNF. As the libdnf API is exported through GObject Introspection, it can be natively used in Perl for the installer.
Why it would be good for Mageia to do it
Porting the installer to use 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 for adding DNF, porting the installer is a requirement for enabling the full migration to DNF.
- Install Mageia using installer
- Upgrade from Mageia 6 to Mageia 7
- Add custom repositories to add to package selection
- Port installer to DNF engine
Software / Packages Dependencies
What could disrupt development of this new feature
If the installer cannot be ported, then this feature cannot be completed.
Early inclusion into Mageia 7 would allow for good appropriation of development and QA resources to make this work.
If this fails to be ready for Mageia 7, then we continue with the current installer code.
The release notes should indicate that Mageia's installer now uses DNF to install/upgrade the system.