From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6690944878080163840 X-Received: by 2002:a19:2005:: with SMTP id g5mr4010799lfg.157.1558508550161; Wed, 22 May 2019 00:02:30 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:ac2:494e:: with SMTP id o14ls110161lfi.4.gmail; Wed, 22 May 2019 00:02:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqzow1ipzxk4yOiyt3vntBp3COAT1gecwd5lmQuFjWsgKv/T6tHXWODn5slqPL0970iFE+mv X-Received: by 2002:ac2:51d1:: with SMTP id u17mr1703392lfm.151.1558508549564; Wed, 22 May 2019 00:02:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558508549; cv=none; d=google.com; s=arc-20160816; b=JamSWFDUPHLXICKWFOsDUMKsa6UQD1UuxoTVGD+skMWNxXZzYORASO8k6L4rxtk3+t D+EGeCcQiWRtnDRWE2Z4CArigRhzYYCsZPilDmLk1cLuvgMgBxLnV5PvsDg0hkllf+au qkffEmZCHWFqy9MGldBVvGc9hrYgnAqxDpu7QugjKnECLimJMonV5M5ql1p5gIJSDhjk r6vhptu6CjLewNpRRIWzF1sVvxhxd2KkC2cnpIYVftJsZPgzan9fzrGa6tWsByLPDKBh jTxc+87tNSrZdfa+I9pNZ4g29hcLWov5D2Pwluv7foGCp6jCw4s0dGRV7XFTHwWAmvIA /4sg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject; bh=aglPseshAP+EVdvyIInBuJRgFo+AY9r4kjAOis/+LnY=; b=m66RUBnv+3R2yGtmC5N4WO6zLXLsnuMuL3MR8EEQM24h7m2TimIwU/rDIgdiNZ2V6h zcrDH1CnJ5YyjpOLQj7ZpF3IEXyI3lsK765zhHPYRpGwChLDYyGe2xlk+dSOZfn4tpAk 4V5dCNHpAesdnivYIEYkliXf351D7xPZFJ5eq9IQcm43/J1hlCeExihtkM/X94RRi24i vygWpgnAkyIHD1Jm0+faM4z2w6IdzvsekY7KXmeN4FkCK4SLItHFE8rkxmSduinHWzn2 /AM9yHBrNXnCUOsdTLIVMtCoZr15Zy/dJoiRfA1p27pyKjluo2RZJYnnTLVyYpLRHC9f o1TA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id p21si2044338ljj.1.2019.05.22.00.02.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 May 2019 00:02:29 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id x4M72Sla028958 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 22 May 2019 09:02:28 +0200 Received: from [167.87.9.78] ([167.87.9.78]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x4M72RO1018562; Wed, 22 May 2019 09:02:27 +0200 Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage To: "Maxim Yu. Osipov" , Claudius Heine , isar-users@googlegroups.com Cc: Claudius Heine References: <20190515101149.22187-1-claudius.heine.ext@siemens.com> <20190515101149.22187-2-claudius.heine.ext@siemens.com> <3745f4ba-e3c9-4d59-22e4-9746c6497f6b@siemens.com> From: Jan Kiszka Message-ID: <80d56fc5-00fa-5508-7fb1-976b4b5c61db@siemens.com> Date: Wed, 22 May 2019 09:02:27 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: 9xWIMgYC4KLL On 22.05.19 08:55, Maxim Yu. Osipov wrote: > On 5/22/19 8:37 AM, Claudius Heine wrote: >> Hi Jan, >> >> On 21/05/2019 18.56, Jan Kiszka wrote: >>> On 15.05.19 12:11, [ext] claudius.heine.ext@siemens.com wrote: >>>> From: Claudius Heine >>>> >>>> isar-bootstrap-host only supports bootstrapping Debian root file >>>> systems. Therefore deactivate any DISTRO_BOOTSTRAP_KEYS from other >>>> distributions. >>> >>> Actually not totally true, as I just realized: What about bootstrapping the >>> buildchroot from a custom debian repo that was differently signed (e.g. >>> because it is a condensed version of upstream)? Seems we do need >>> HOST_DISTRO_BOOTSTRAP_KEYS, right? >> >> You are right, I haven't considered that case. Well, the next task on the todo >> list should probably be to refactor and streamline the isar-bootstrap, and >> especially the host bootstrap process and fix those kind of issues while doing >> that. >> >> There are a lot of possible customization options gained if the current giant >> bootstrap function would be split up, similar to how the rootfs system works >> in the pre-processing patchset. >> >> Maybe it makes sense to also start renaming "host" and "target" to be >> compatible with the gcc nomenclature [1] in that patchset. I am a bit >> reluctant to do so, because of the breakage involved. But the further we wait, >> to more stuff will break downstream. >> >> The plan would be to rename all occurrences of "host" to "build" and "target" >> to "host". That would lead to the following recipe changes: > > >> "buildchroot-host" -> "buildchroot-build" >> "buildchroot-target" -> "buildchroot-host" >> "isar-bootstrap-host" -> "isar-bootstrap-build" >> "isar-bootstrap-target" -> "isar-bootstrap-host" > > >> I am on the fence of that change. Correctness vs. no-breakage >> >> Any comments about that? > > I would prefer to avoid such a renaming taking into account needed efforts and > possible confusion for current Isar users. > Is that build/host scheme then also in line with Debian naming? Then there will be eventually no way around it anyway. But we really need to do this thoroughly, specifically /wrt to user-visible interfaces, so that it will be one cut only. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux