public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Claudius Heine <ch@denx.de>,
	"Maxim Yu. Osipov" <mosipov@ilbers.de>,
	claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage
Date: Fri, 26 Apr 2019 13:31:38 +0200	[thread overview]
Message-ID: <ae7f4d77-c495-d223-9ba9-5524ffd17f4c@siemens.com> (raw)
In-Reply-To: <155626421155.10914.2537647574220599237@ardipi>

On 26.04.19 09:36, Claudius Heine wrote:
> Hi Maxim,
> 
> Quoting Maxim Yu. Osipov (2019-04-25 20:20:59)
>> On 4/25/19 3:44 PM, claudius.heine.ext@siemens.com wrote:
>>> From: Claudius Heine <ch@denx.de>
>>>
>>> isar-bootstrap-host only supports bootstrapping Debian root file
>>> systems. Therefore deactivate any DISTRO_APT_KEYS from other
>>> distributions.
>>>
>>> Signed-off-by: Claudius Heine <ch@denx.de>
>>> ---
>>>    meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb | 2 ++
>>>    1 file changed, 2 insertions(+)
>>>
>>> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb b/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb
>>> index 08b068f..3e96281 100644
>>> --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb
>>> +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb
>>> @@ -12,6 +12,8 @@ DEPLOY_ISAR_BOOTSTRAP = "${DEPLOY_DIR_BOOTSTRAP}/${HOST_DISTRO}-${HOST_ARCH}"
>>>    ISAR_BOOTSTRAP_LOCK = "${DEPLOY_DIR_BOOTSTRAP}/${HOST_DISTRO}-${HOST_ARCH}.lock"
>>>    
>>>    require isar-bootstrap.inc
>>> +# We only build debian host buildchroot environments
>>> +DISTRO_APT_KEYS = ""
>>
>>   From the first glance this modification limits functionality.
>> It looks like a hack and I would suggest to avoid this modification.
> 
> Well it is a fix and that limited functionality was already present but
> just implicit, hidden behind some bug and the cleanup just made it
> appear.
> 
>> Some time ago I thought about introduction of HOST_DISTRO_APT_KEYS to
>> avoid confusion between target and host apt keys.
> 
> Good idea. But that would be a new feature/improvement.
> 

If that is just about adding and documenting another variable, let's not discuss 
about when and who because just doing that will already be faster, even if it's 
a "drive-by" improvement /wrt this patchset.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2019-04-26 11:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 13:44 [PATCH v4 0/9] Cleanup rootfs creation claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 1/9] isar-bootstrap-host: disable DISTRO_APT_KEYS usage claudius.heine.ext
2019-04-25 18:20   ` Maxim Yu. Osipov
2019-04-26  7:36     ` Claudius Heine
2019-04-26  8:41       ` Maxim Yu. Osipov
2019-04-26 10:39         ` Claudius Heine
2019-04-26 10:45           ` Claudius Heine
2019-04-26 11:22             ` Maxim Yu. Osipov
2019-04-26 11:47               ` Jan Kiszka
2019-04-30  9:34         ` Andreas Reichel
2019-04-30 13:30           ` Maxim Yu. Osipov
2019-04-30 15:22             ` Andreas Reichel
2019-04-30 15:30               ` Jan Kiszka
2019-04-30 15:46               ` Maxim Yu. Osipov
2019-05-02 12:14                 ` Andreas Reichel
2019-04-26 11:31       ` Jan Kiszka [this message]
2019-04-26 11:50         ` Jan Kiszka
2019-05-14  9:22           ` Fwd: " Maxim Yu. Osipov
2019-05-14 11:32           ` Claudius Heine
2019-05-14 11:35             ` Claudius Heine
2019-04-25 13:44 ` [PATCH v4 2/9] isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 3/9] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 4/9] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 5/9] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 6/9] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 7/9] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 8/9] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-04-25 13:44 ` [PATCH v4 9/9] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext

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=ae7f4d77-c495-d223-9ba9-5524ffd17f4c@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ch@denx.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=mosipov@ilbers.de \
    /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