From: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
To: isar-users@googlegroups.com
Subject: How to update os-release information
Date: Tue, 19 Jan 2021 08:49:09 +0100 [thread overview]
Message-ID: <c107a46b-59de-ed2f-fcb7-b938218eb03d@siemens.com> (raw)
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/
next reply other threads:[~2021-01-19 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 7:49 Silvano Cirujano Cuesta [this message]
2021-01-19 8:02 ` Silvano Cirujano Cuesta
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=c107a46b-59de-ed2f-fcb7-b938218eb03d@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