Bug 1149568
Summary: | /etc/os-release should be a symlink to /usr/lib/os-release | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rahul Sundaram <metherid> |
Component: | fedora-release | Assignee: | Dennis Gilmore <dennis> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | dennis, jdisnard, pbrobinson, zbyszek |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-02-10 17:03:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1149569 | ||
Bug Blocks: |
Description
Rahul Sundaram
2014-10-06 05:52:58 UTC
It should be a relative symlink according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755394 sorry I do not see this as a bug The idea is to move os-release file to /usr, because it describes the installation in /usr. Putting in in /etc was a mistake, because it is not something configurable. So /etc/os-release is the legacy location, and /usr/lib/os-release is the canonical one now. Symlink needs to be provided for compatibility. I think that since fedora-relese provides the file, it should also provide the symlink. Please reconsider moving the file to /usr/lib and providing a symlink /etc/os-release → ../usr/lib/os-release. We can also provide the symlink in the systemd package if you prefer. I don't think it makes much difference, except that both packages will have to be updated together when the move happens. There are two outstanding issues: - this - #1182635 It would be nice to resolve them in one update, but #1182635 should be updated with the details first. Committed upstream, will be in F-22/F-23 shortly once we've finished the branch |