Bug 1282430 - Rename /etc/os.release.d to /etc/os-release.d
Rename /etc/os.release.d to /etc/os-release.d
Product: Fedora
Classification: Fedora
Component: fedora-release (Show other bugs)
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: Dennis Gilmore
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2015-11-16 06:40 EST by Fabian Deutsch
Modified: 2015-12-11 13:32 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-11 13:32:46 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fabian Deutsch 2015-11-16 06:40:24 EST
Description of problem:
The fedora-release rpm provide some files to override variables of /etc/os-release (see http://pkgs.fedoraproject.org/cgit/fedora-release.git/tree/fedora-release.spec#n117)

But the directory which has these overrides is named /etc/os.release.d - even if the files within override variables of /etc/os-release (note the dot vs dash).

It would be better to rename the dir /etc/os.release.d to /etc/os-release.d to match the semantics.
Comment 1 Zbigniew Jędrzejewski-Szmek 2015-11-16 07:51:58 EST
Agreed. It would be nice to rename this for consistency.
Also /usr/lib/os.release.d.
Comment 2 Stephen Gallagher 2015-11-16 08:23:47 EST
Honestly, I need a more compelling reason than "for consistency" to make this change. It's trickier than one might think to ensure that all of the symlinks get migrated properly to a new directory path (particularly in cases where someone has intentionally removed the symlink in order to drop their own version into /etc) and I'd prefer not to break upgrades for anything short of an actual bug.
Comment 3 Fabian Deutsch 2015-11-16 08:34:50 EST
Can't we just create a symlink from os-release.d to os.release.d?

The thign is that the convention <name> <name>.d/* to override works "everywhere", except for os-release.
Comment 4 Stephen Gallagher 2015-11-16 08:47:22 EST
How does that help your complaint? We'd now be polluting /usr/lib with *both* pathnames. That just adds confusion in my mind.

Also, just off the top of my head, I can cite apache's "conf.d" as not matching your convention.

Lastly, I don't disagree with your assertion that this was a mistake. It was actually a typo on my part that got overlooked in patch-review and is now non-trivial to correct. Like I said in my previous comment: it's not worth making this change just for aesthetic reasons. If it solved an *actual problem*, that would be a different situation.
Comment 5 Fabian Deutsch 2015-11-16 08:52:21 EST
Yes, I know it was a mistake. I still wanted to raise it, because I'd really like to get this consistent - maybe even in the far future.

But this dir is not to old, so I wonder how much impact a change had.

In the end I agree that it's not fixing a bug.
Comment 6 Stephen Gallagher 2015-11-16 08:57:20 EST
(In reply to Fabian Deutsch from comment #5)
> Yes, I know it was a mistake. I still wanted to raise it, because I'd really
> like to get this consistent - maybe even in the far future.
> But this dir is not to old, so I wonder how much impact a change had.

Well, this package is installed on every Fedora system and has effects that include:
* How systemctl operates (it reads from /usr/lib/os-release)
* How the firewall is set up (it's dependent on the VARIANT_ID field)
* Which systemd presets file is used.

So screwing this up would have a very significant negative effect on systems. We've already had a couple (minor, fortunately) bugs with the conversion to the drop-dir in the first place and I'd prefer not to fix a non-problem and risk breaking people.

> In the end I agree that it's not fixing a bug.

Thanks, I know it's annoying. It offends my sense of perfectionism too, but I feel that the risks are too high to justify it.
Comment 7 Fabian Deutsch 2015-11-16 09:32:47 EST

Thanks for discussing. I say darn, and move on.
Comment 8 Stephen Gallagher 2015-12-11 09:34:25 EST
So, I took another look at this today while working on BZ#1288205 and I realized that I probably can manage to convert this over to a better directory with minimal risk. Instead of os-release.d, I think I'm going to change it to /usr/lib/fedora.

Here's my reasoning: os-release.d sounds like it should belong with the package that processes os-release (systemd). This is confusing for users. Furthermore, this directory now contains more than just the os-release symlinks: it contains the /etc/issue symlink for server and with BZ#1288205 will also contain edition-specific presets.

Given those usages, I think calling it /usr/lib/fedora makes the most sense. It should be much clearer.
Comment 9 Stephen Gallagher 2015-12-11 11:28:41 EST
Comment 10 Dennis Gilmore 2015-12-11 13:32:46 EST
I am closing this notabug.  there are way too many corner cases that can go wrong, if the change fixed a real issue other than sematics I would be willing to fix it, and deal with any fallout

Note You need to log in before you can comment on or make changes to this bug.