What | Removed | Added |
---|---|---|
CC | behlert@suse.com, fcrozat@suse.com | |
Flags | needinfo?(fcrozat@suse.com), needinfo?(behlert@suse.com) |
(In reply to Mikhail Kasimov from comment #7) > From ML: "We only have few days left to define what is in /etc/os-release > for 15 in case it's suboptimal." (c) > > So, short summary to discuss and to work out the final decision: > > Solution to have for ID= field: > ================================ > > ID="opensuse-leap" | "opensuse-tumbleweed" | "opensuse-leap-%projectname%" | > "opensuse-tumbleweed-%projectname%" > > ID="sles" | "sled" | "caasp" | "sles-%projectname%" | "sled-%projectname%" | > "caasp-%projectname%" > ================================ > > Solution to have for ID_LIKE= field: > ===================================== > 2.1. To add ID_LIKE= field into /etc/os-release file for all commercial SUSE > products versions: SLES, SLED. CaaSP and so on to be synchronized with > non-commercial ones. > > 2.2. For all non-commercial SUSE products versions to define: > > ID_LIKE="opensuse" > > 2.2. For all commercial SUSE products versions to define: > > ID_LIKE="suse" > ===================================== > > Richard, Ludwig,..., -- any reaction, suggestion, decision? Thanks! I think it's unreasonable to expect SUSE to change their use of os-release this late in their development process. Stefan, Frederic, do I mis-read the situation? Ideally this is something we probably should tidy up, as it will dramatically ease a lot of painpoints for tools like Saltstack. Regardless of the situation in SLE*, I give my +1 to the proposed openSUSE changes, though I would prefer ID_LIKE="suse opensuse" because ID_LIKE="suse" would allow us to provide a single global match for "all *SUSE distros" (including SLE*), assuming SLE adopt this approach in this future. However even then we may well need a more restrictive match for "all openSUSE distros" (excluding SLE*), which would be fulfilled by ID_LIKE="opensuse" Given the os-release standard allows multiple values in this field, we might as well use it.