Bug ID 1088306
Summary Mess in /etc/os-release files for different openSUSE branches
Classification openSUSE
Product openSUSE Distribution
Version Leap 42.3
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter mikhail.kasimov@gmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Hello!

Found some mess in /etc/os-release naming scheme. Cosmetic mess, but, anyway,
it's desirable to fix it to have unified /etc/os-release items-style.

Not sure of Component section to file this report, in particular, because it is
applicable both for Leap and Tumbleweed branches. Feel free to move report, if
needed.

Deal:
=====


The mess is in ID= and ID_LIKE= fields for Leap and Tumbleweed branches.


For example on Leap 42.3/15.0/Tumbleweed:
================================
cat /etc/os-release

...
ID=opensuse <-- missed double-quotes
ID_LIKE="suse"
...
================================

At the same time Tumbleweed Kubic:
================================
...
ID="opensuse-tumbleweed-kubic" <-- why not "opensuse" as it is done for
Tumbleweed?
ID_LIKE="suse opensuse" <-- why not also "suse" as it is done for
Leap/Tumbleweed?
...
================================



Solution to have:
================================

1. For Leap branch:

ID="opensuse-leap"
ID_LIKE="suse"

2. For Tumbleweed branch:

ID="opensuse-tumbleweed"
ID_LIKE="suse"

3. For Tumbleweed-based projects (like it is done for Kubic)

ID="opensuse-tumbleweed-%project_name%"
ID_LIKE="suse"

4. For Leap-based projects (to be reserved)

ID="opensuse-leap-%project_name%"
ID_LIKE="suse"
================================


If you take a look on SLES/SLED/CaaSP branches, you'll see, that all of them
have clearly defined ID= fields:

ID="sles"
ID="sled"
ID="caasp"

respectively. And note, double-quotes for ID= field are present everywhere,
except of Leap branch. So, let's have clearly defined mess-free/unified ID=
fields for openSUSE branches too.

Thanks!


You are receiving this mail because: