From Mageia wiki
Jump to: navigation, search


Summary

Port the installer to use DNF.

Owner

  • Name: Neal Gompa
  • Email: ngompa13@gmail.com

Resources

This will require efforts by the installer developers to port the installer to DNF.


Current status

  • Targeted release: Mageia 7
  • Last updated: 2017/09/16
  • Percentage of completion: 0%


Detailed Description

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.


Test case

  • Install Mageia using installer
  • Upgrade from Mageia 6 to Mageia 7
  • Add custom repositories to add to package selection

Tasks

  • Port installer to DNF engine


Software / Packages Dependencies

  • DrakInstall
  • libdnf


What could disrupt development of this new feature

If the installer cannot be ported, then this feature cannot be completed.

Planning

Early inclusion into Mageia 7 would allow for good appropriation of development and QA resources to make this work.

Contingency

If this fails to be ready for Mageia 7, then we continue with the current installer code.

Release Notes

The release notes should indicate that Mageia's installer now uses DNF to install/upgrade the system.

Documentation

Associated Bugs

Packager comments