Future of the DNF package management stack
summary
DNF now has about 4,000 commits and roughly 90 active contributors across projects, a redesigned new history database in Fedora 29, and a C++ libdnf API that generates Python bindings; a C plugin API exists but is unstable. Performance drops between Fedora 27 and 29 shrink to a couple seconds dominated by repo loading. Planned work includes chunk compression for metadata, a shared work cache with microdnf/packagegate, unified libdnf by Fedora 32, CI tests, and a possible DNF daemon.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:46Agenda
- 1:14What is DNF?
- 2:30DNF stack overview - stats
- 4:20Achievements over the last year (1)
- 5:43Performance Improvement
- 7:26Achievements over the last year (2)
- 9:20Existing DNF stack architecture
- 10:25Unified DNF stack architecture
- 11:37Roadmap (1)
- 12:57Integration Testing
- 13:29Roadmap (2)
- 14:33Future Vision (F33+)
related talks
37mDNF5 - Next Generation of Software Management
41mSpeeding up DNF and RPM using Copy on Write
47m35 Fedora releases in 35 minutes: a look back with lessons for any project
01h 09m35 Fedora Releases in 30 Minutes (plus Q&A)
29mTowards stronger checks on dependencies and compose inputs in Fedora
15mrebuilddb at Facebook scale
48mFedora Automated Testing State of the Art: Not Quite CI for Distributions, but...
16mlightning talk, CentOS Dojo, DevConf.us