From Fedora Project Wiki
< Changes
No edit summary |
(→Scope) |
||
| Line 76: | Line 76: | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: | ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Change affects whole distro rather than some derivable | ||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | ||
* Policies and guidelines: | * Policies and guidelines: Mothing is required <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
* Trademark approval: N/A (not needed for this Change) | * Trademark approval: N/A (not needed for this Change) | ||
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
Revision as of 16:05, 5 July 2017
Unified database for DNF
Summary
Replacing obsoleted YUM/DNF databases (yumdb, historydb, groups.json) with new unified sqlite database adapted to the current needs of DNF.
Owner
- Name: Eduard Čuba, Igor Gnatenko
- Email: ecuba@redhat.com, ignatenkobrain@fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 27
- Last updated: 2017-07-05
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Unified software database for DNF is replacing outdated and obsolete databases behind the DNF. It comes with shared library for accessing the database used by DNF and PackageKit. Library providing database access should be part of libdnf.
Benefit to Fedora
Using single unified database with shared interface enhances data integrity, safety and performance of package managers in Fedora. Database is easily expandable for new features(Fedora modularity support).
Scope
- Proposal owners: Port DNF to SWDB (patches has been already sent), Port PackageKit to SWDB
- Other developers: PackageKit developers should review proposed changes in libdnf for logging PackageKit transactions into SWDB instead of yumdb. In addition PackageKit developers should consider using SWDB for reading transaction data instead of using its own backend.
- Release engineering: #6886 (a check of an impact with Release Engineering is needed)
- List of deliverables: Change affects whole distro rather than some derivable
- Policies and guidelines: Mothing is required
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Data from obsolete databases are migrated to SWDB with first use of ported DNF. There is no backward migration available.
How To Test
Use DNF in normal operation (especially history commands).
User Experience
Increase of history related DNF commands performance.
Dependencies
Changing DNF databases in the background should not affect other packages.
Contingency Plan
- Contingency mechanism: Write tool to convert to old db format and revert change
- Contingency deadline: Beta Freeze
- Blocks release? Yes (not sure)
- Blocks product? -
Documentation
Not written yet.