From: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: How to update os-release information
Date: Tue, 19 Jan 2021 09:02:09 +0100 [thread overview]
Message-ID: <43845dc5-350f-8b7d-554e-84579152404e@siemens.com> (raw)
In-Reply-To: <c107a46b-59de-ed2f-fcb7-b938218eb03d@siemens.com>
BTW, according the Debian Derivatives Guidelines [3] the list of files to modify for de-/re-branding are:
/etc/issue
/etc/issue.net
/etc/dpkg/origins/default (symlink to distribution information file)
/etc/os-release (symlink to /usr/lib/os-release)
/usr/lib/os-release
/usr/share/base-files/motd
No matter how, we should probably provide recipes for supporting the whole de-/re-branding, not only /etc/os-release, right?
Silvano
[3] https://wiki.debian.org/Derivatives/Guidelines#De-.2FRe-branding
On 19/01/2021 08:49, [ext] Silvano Cirujano Cuesta wrote:
> Hi,
>
> as reported [1], the current code (function "update_etc_os_release" in "meta/classes/image-postproc-extension.bbclass") is changing /etc/os-release in a wrong way... Now the question is, which is the right way?
>
> In some internal discussions I've realized that the approach that I'm proposing is technically Ok, but doesn't appear to be the common one. Debian-derived distros strongly changing vanilla Debian (e.g. Ubuntu and Purism) are creating their own "base-files" packages containing their information. I'd propose contacting upstream Debian [2] to find out which is the best approach and why.
>
> Regards,
>
> Silvano
>
> [1] https://groups.google.com/g/isar-users/c/Jr3bTPumH-w
>
> [2] https://lists.debian.org/debian-derivatives/
>
prev parent reply other threads:[~2021-01-19 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 7:49 Silvano Cirujano Cuesta
2021-01-19 8:02 ` Silvano Cirujano Cuesta [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43845dc5-350f-8b7d-554e-84579152404e@siemens.com \
--to=silvano.cirujano-cuesta@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox