From Fedora Project Wiki
< Changes
Chrismurphy (talk | contribs) No edit summary |
Chrismurphy (talk | contribs) No edit summary |
||
| Line 65: | Line 65: | ||
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* change in rpm and dnf-data packages | |||
* create the new path instead of old | |||
* create symlinks for the old path to new path | |||
* changes in SElinux policy | |||
* Release engineering: [https://pagure.io/releng/issue/10441 #Releng issue 10441] | * Release engineering: [https://pagure.io/releng/issue/10441 #Releng issue 10441] | ||
| Line 79: | Line 83: | ||
== 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? --> | ||
Change will be applied on upgrades to Fedora 36. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 97: | Line 102: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
* Clean install or upgrade an existing Fedora system | |||
* Note the changes | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 112: | Line 119: | ||
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system. | ||
--> | --> | ||
Users will notice (a) symlinks in the old locations for the databases, pointing to the new locations; and (b) paths existing in the new locations. Otherwise the change should be invisible to them. | |||
== Dependencies == | == Dependencies == | ||
Revision as of 17:49, 6 December 2021
Relocate RPM/DNF databases to /usr
Summary
Currently, the RPM and DNF databases are located in /var. Let's move them to /usr.
Owner
- Name: Chris Murphy
- Email: chrismurphy@fedoraproject.org
Current status
- Targeted release: Fedora Linux 36
- Last updated: 2021-12-06
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Current location
/var/lib/rpm /var/lib/dnf
New location
/usr/lib/sysimage/rpm /usr/lib/sysimage/dnf
Feedback
Benefit to Fedora
The RPM and DNF databases describe the state of (primarily) /usr. Storing these databases in /usr will more easily facilitate OS rollback, without affecting /var.
Scope
- Proposal owners:
- Other developers:
- change in rpm and dnf-data packages
* create the new path instead of old * create symlinks for the old path to new path
- changes in SElinux policy
- Release engineering: #Releng issue 10441
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Helps align Fedora variants with each other. rpm-ostree based systems already use /usr/lib/
Upgrade/compatibility impact
Change will be applied on upgrades to Fedora 36.
How To Test
- Clean install or upgrade an existing Fedora system
- Note the changes
User Experience
Users will notice (a) symlinks in the old locations for the databases, pointing to the new locations; and (b) paths existing in the new locations. Otherwise the change should be invisible to them.
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)