I do really agree that how we offer branding should be covered in a GLEP, and be very easy for downstream offshoots of Gentoo to follow. This would prevent future concerns like the Ubuntu branding / modified VM spats.
[snip awilfox's superb proposal; I agree with all of the reasons and
outcomes, but think a little bit more structure & flexibility are
needed].
On Mon, Dec 05, 2016 at 08:46:53AM +0100, Michał Górny wrote:
> Strictly speaking, it could use $EPREFIX/etc/os-release which has all
> the info you need, is installed by baselayout and doesn't require
> special wrappers to print it.
...
> The other alternative is to provide an eclass that reads data from
> $EPREFIX/os-release and supplies it to the packages that need it.
I've been wondered about this, since reading awilfox's PR, and I have
some tweaks & extensions to offer to their proposal. This resolves all
of the drawbacks noted by mgorny, supports branding information via
profiles (or other means).
0. This proposal is centered around using os-release, as a
cross-distribution model.
1. ebuilds: Add eclass to export all variables from /etc/os-release with
a prefix:
OS_RELEASE_ID
OS_RELEASE_NAME
OS_RELEASE_PRETTY_NAME
OS_RELEASE_BUG_REPORT_URL
etc
(I'm happy to bikeshed the name of the variable prefix).
1.1. Upstream packages that natively read from /etc/os-release will
automatically be supported.
1.2. Could potentially be in base.eclass.
2. Introduce a new virtual: virtual/os-branding.
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)
4. sys-apps/baselayout:
4.1. Move all branding pieces OUT of sys-apps/baselayout, into
per-distro packages, that satisfy virtual/os-branding.
4.2. Depend on virtual/os-branding (maybe implicit via the eclass
above?)
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer
E-Mail : robb...@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
signature.asc
Description: Digital signature
