From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6917993065941565440 X-Received: by 2002:a05:600c:4105:: with SMTP id j5mr4027947wmi.0.1613033375046; Thu, 11 Feb 2021 00:49:35 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:4482:: with SMTP id r124ls2515669wma.1.canary-gmail; Thu, 11 Feb 2021 00:49:34 -0800 (PST) X-Google-Smtp-Source: ABdhPJzuIb9xY7Clz3wiM+jOh9Pe6xY2ZkvpST0EC5plxR+fjkS5EciE9KqU5SCkUKX3/uwGmg1D X-Received: by 2002:a1c:99c1:: with SMTP id b184mr3982008wme.163.1613033374085; Thu, 11 Feb 2021 00:49:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613033374; cv=none; d=google.com; s=arc-20160816; b=wgMJHOr2RZ0LhL6HNFH6uT3VPrKrOU4bDSSvc06I3tM8IdKpCDXqukndcHCIJNs7iC iDGZFEln0sdC/wI0AwympabQL2GixVKzzhRSjJFHyeyD2JqATqBbbr0k4E0mXlfL3AOg yRhK5t09xrdN1ciMGoPTk6RMsHcDWfHt7mXA3NSSNAxXYO7JTl92tSiLVVR2w9AAOp2X OmxSWAruxyB95oUXYG/7BEad5/M8vxPcoim0rvFdiV1YQBNE2ArqB4e57ypNm9SddUXq L04uEDmL4csT7O7fF+vIaiaAI4rihY1aNZB6FovveC8aQ5OsOHutbtySg4d/VcVqei78 r1Cg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=IIlMHh6TJFZ4QP+D4s+ryZK4NteyWQ4+cXIx0yVKQtQ=; b=L8IiXFqPEt+c1BTdJzhzxvLrBikiD46libyteHYO0f4DgYdbS2nfpnc8VJEd25WzBN Gq55kkJKo40dBDjCFS5w3IfFdsYSrPL0hTzziVAYScloPgYup3huRVvMszyr4JjOTshi VdXh9O8mFRN3f6VF1aNNCWebdW7T8aZsztEmjQgPh8y7VOV84xmcqAT3tEjbxfuEGuUw JpLd0JP8TOE+Iy5RgqY3EZ8PtQK2TSJoulo8fSt9rHOCf7SfIhYKWQtFZkyfR9fKyY+9 y92aeKXcr16g1FOaj/qmQOG4jgQGb1E3dE7+aFPOuv8cMwbsL68jZw6UbEzgd5Ch/nds cxYw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id z16si238323wml.1.2021.02.11.00.49.33 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Thu, 11 Feb 2021 00:49:34 -0800 (PST) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 11B8nV74016305 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 11 Feb 2021 09:49:33 +0100 Date: Thu, 11 Feb 2021 09:49:31 +0100 From: Baurzhan Ismagulov To: isar-users Subject: Re: image-postproc-extension.bbclass modifying /etc/os-release Message-ID: <20210211084931.GB20742@yssyq.m.ilbers.de> Mail-Followup-To: isar-users 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0fa156df-7943-47ce-86a6-cf02fe5d4d0dn@googlegroups.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: sFxlZfr7NGBV 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). With kind regards, Baurzhan.