From Fedora Project Wiki
< Changes
(→Scope) |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 23: | Line 23: | ||
== Summary == | == Summary == | ||
Replacing obsoleted YUM/DNF databases (yumdb, historydb, groups.json) with new unified sqlite database adapted to the current needs of DNF. | Replacing obsoleted YUM/DNF databases (yumdb, historydb, groups.json) with new unified sqlite database adapted to the current needs of DNF. | ||
== Owner == | == Owner == | ||
| Line 30: | Line 29: | ||
This should link to your home wiki page so we know who you are. | This should link to your home wiki page so we know who you are. | ||
--> | --> | ||
* Name: [[User:edynox|Eduard Čuba | * Name: [[User:edynox|Eduard Čuba]] | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: ecuba@redhat.com | * Email: ecuba@redhat.com | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
| Line 61: | Line 60: | ||
== Benefit to Fedora == | == 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( | 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 (Modularity support in DNF will use SWDB). | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
== Scope == | == Scope == | ||
* Proposal owners: Port DNF to SWDB (patches has been already sent), [[GSOC_2017/Student_Application_edynox|Port PackageKit to SWDB]] | * Proposal owners: Port DNF to SWDB (patches has been already sent), [[GSOC_2017/Student_Application_edynox|Port PackageKit to SWDB]] | ||
| Line 79: | Line 77: | ||
<!-- 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: Nothing 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. --> | ||
| Line 137: | Line 135: | ||
--> | --> | ||
[[Category: | [[Category:ChangePageIncomplete]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 08:25, 8 August 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
- Email: ecuba@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 27
- Last updated: 2017-08-08
- 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 (Modularity support in DNF will use SWDB).
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: Nothing 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.