From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6917993065941565440 Date: Thu, 11 Feb 2021 02:34:00 -0800 (PST) From: "vijaikumar....@gmail.com" To: isar-users Message-Id: In-Reply-To: <20210211084931.GB20742@yssyq.m.ilbers.de> References: <0beb8d2d-5141-647c-a831-8693276c957a@siemens.com> <333bd498-2e79-bb2d-ef84-3f6ab68a68b9@denx.de> <6f4b945f-7763-49ee-a8c5-2e02d450a2e0n@googlegroups.com> <6473666c-a754-0512-0000-a072f4530d3f@siemens.com> <3bbb9c63-6f3c-d0c9-416e-31edb430642f@siemens.com> <20210210092248.GX20742@yssyq.m.ilbers.de> <0fa156df-7943-47ce-86a6-cf02fe5d4d0dn@googlegroups.com> <20210211084931.GB20742@yssyq.m.ilbers.de> Subject: Re: image-postproc-extension.bbclass modifying /etc/os-release MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_572_4395067.1613039640153" X-TUID: efwYxWwg7H2X ------=_Part_572_4395067.1613039640153 Content-Type: multipart/alternative; boundary="----=_Part_573_412391721.1613039640153" ------=_Part_573_412391721.1613039640153 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On Thursday, February 11, 2021 at 2:19:35 PM UTC+5:30 i...@radix50.net wrote: > On Wed, Feb 10, 2021 at 09:54:39PM -0800, vijaikumar....@gmail.com wrote: > > Since ISAR is providing that information by default, and people use it > based > > on upstream trust, we should probably have that information in a way > that it > > is usable even after an upgrade. Or not provide it at all. I am more > > inclined to > > base-files approach here since we know that /etc/os-release is > maintained > > by it. > > Since providing another file is not the recommended way, as per Debian, > we > > should probably provide the isar information in /etc/os-release through > > custom > > base-files in upstream isar for reference. > > > > Do you feel it is a strong enough reason to have custom base-files in > ISAR? > > Clean or nothing -- fair enough. I don't have strong feelings that we > should > provide that information at all :) , but I admit it is handy after we have > it. > As long as Isar doesn't become a distro, I'm fine with providing > base-files as > it cleans things up, especially long-term (updates). Ok. In that case, I will try preparing a patch and send it for review sometime soon. Thanks, Vijai Kumar K > > With kind regards, > Baurzhan. > ------=_Part_573_412391721.1613039640153 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

On Thursday, February 11, 2021 at 2:19:35 PM UTC+5:30 i...@radix50.net wrote:
On Wed, Feb 10, 2021 at 09:54:39PM -0800, vijaikumar....@gmail.com wrote:
> Since ISAR is providing that information by default, and people use it based
> on upstream trust, we should probably have that information in a way that it
> is usable even after an upgrade. Or not provide it at all. I am more
> inclined to
> base-files approach here since we know that /etc/os-release is maintained
> by it.
> Since providing another file is not the recommended way, as per Debian, we
> should probably provide the isar information in /etc/os-release through
> custom
> base-files in upstream isar for reference.
>
> Do you feel it is a strong enough reason to have custom base-files in ISAR?

Clean or nothing -- fair enough. I don't have strong feelings that we should
provide that information at all :) , but I admit it is handy after we have it.
As long as Isar doesn't become a distro, I'm fine with providing base-files as
it cleans things up, especially long-term (updates).

Ok. In that case, I will try preparing a patch and send it for review sometime
soon.

Thanks,
Vijai Kumar K
 

With kind regards,
Baurzhan.
------=_Part_573_412391721.1613039640153-- ------=_Part_572_4395067.1613039640153--