On Thu, Dec 15, 2016 at 4:49 PM, Robin H. Johnson <robb...@gentoo.org> wrote: > 3. The distro branding package (v1) (providers of virtual/os-branding): > - MUST have NO build dependencies that require execution (this could > be the very first package in a bootstrap). > - MUST install /etc/os-release > - /etc/os-release MUST provide the following values > - NAME, ID, PRETTY_NAME, HOME_URL, > - /etc/os-release MAY provide other values. > - MAY provide hardcoded values for /etc/os-release > - MAY read values from profiles for /etc/os-release > - MAY install any other branding files (logos, artwork, trademark, > notices, etc)
A technical note here: we should probably install /usr/lib/os-release instead of /etc/os-release. https://www.freedesktop.org/software/systemd/man/os-release.html Quoting the above: The file /etc/os-release takes precedence over /usr/lib/os-release. Applications should check for the former, and exclusively use its data if it exists, and only fall back to /usr/lib/os-release if it is missing. Applications should not read data from both files at the same time. /usr/lib/os-release is the recommended place to store OS release information as part of vendor trees. /etc/os-release should be a relative symlink to /usr/lib/os-release, to provide compatibility with applications only looking at /etc. A relative symlink instead of an absolute symlink is necessary to avoid breaking the link in a chroot or initrd environment such as dracut.
