(In reply to Richard Brown from comment #8) > (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. That sounds sane. Indeed, ML-message bumped me up. :) > 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. I also was thinking about CPE_NAME= field to parse, but external developers will pay their attention on the most obvious and generic variations, like ID= and ID_LIKE= fields, I suppose. And parsing CPE_NAME= field is extremely lame method, personally, (e.g. cat /etc/os-release | grep '^CPE_NAME=' | awk -F= '{print $2}' | awk -F: '{print $3,$4,$5,$6}' | sed 's/\"//g'), although CPE_NAME= gives much better possibilities to match distro. And it is present both in SLE-based and openSUSE-based distros instead of ID_LIKE= field (see 2.1).