From Fedora Project Wiki
< Changes
Chrismurphy (talk | contribs) No edit summary |
Chrismurphy (talk | contribs) No edit summary |
||
Line 49: | Line 49: | ||
<pre>/usr/lib/sysimage/rpm | <pre>/usr/lib/sysimage/rpm | ||
/usr/lib/sysimage/dnf</pre> | /usr/lib/sysimage/dnf</pre> | ||
Line 59: | Line 57: | ||
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`. | 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 == | == Scope == | ||
Line 75: | Line 74: | ||
* Alignment with Objectives: | * Alignment with Objectives: | ||
Helps align Fedora variants with each other. rpm-ostree based systems already use /usr/lib/ | |||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == |
Revision as of 17:28, 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:
- 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
How To Test
User Experience
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)