From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6690944878080163840 X-Received: by 2002:a05:6402:648:: with SMTP id u8mr87039079edx.176.1558510266393; Wed, 22 May 2019 00:31:06 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a50:92d5:: with SMTP id l21ls351830eda.6.gmail; Wed, 22 May 2019 00:31:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqzl/xpWPmk/lbtlzt/05Yu8gLTaV0XEx0hp+spMECokK7QXuty6jaciYgmMTrTdKn8PKlmY X-Received: by 2002:a50:cc0c:: with SMTP id m12mr59376109edi.8.1558510265986; Wed, 22 May 2019 00:31:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558510265; cv=none; d=google.com; s=arc-20160816; b=nK2K2lcNFfX0cXydlv6ozEIjztfmn30asMzMqU22saLvqfB4no5dw0ocxH8tHekeoR eGfpc+xCECuq00G7azB+8zJ7GUPE+Na8gpFSQjqjRe0iUICsJi0LDHg8RgdvGpttAwRc pE/W9GUYD64bSB4wGNXQPOx4dTk/JG5DKisBErjPTRdkQ37G09LuKCUJJAFSw4602Lij VkaDNy9gQ92g8jwWu9GIgR/TLXeQhGd2aIXbLKQIz0h3K3P62Tc5EpH65SqGfQn+3/v3 4qhSZcK7No3nE7OzPNIku6dj56I2DEcEZE/PLQ4VudvPKeXRC6GIaGHYFdu1/sLVAUbw KUQA== 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=km9CtNgQ5lsuYjXPyOOij/FDLX+0lSRocK4NAU3o6ko=; b=FeQIR4dpOLA8NhMFW4K+Udp3MF2jlr4650DLr1+9uYjt1ozW6j7Domg1CO/jHaA9o7 U5LlB5lqITc3HQ3JkP7JNY+h0vqArIq1z9KEVCfst36ryLrOM9MXQJdki4fa3eoQQ8Cf YQh4XYsblNlewjwXjQP+i2tL7SSMdgj5X55lfXjA56pK9p5DG+QnBJGjznbH6E2buYZt aBvuZpVZPbLl/vuvuYMqBxlviAUKJ3LSDbZEN8L3trxHo+iQL2l9RfPssdYY+CK75ut5 guXlL7+qY47AoCZQTlanLpU4C2QXCL3DGBlBkScNJCSxNwCyrlD++yuOBZOONwa/NhL3 H7tQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id w5si2566267edw.1.2019.05.22.00.31.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 May 2019 00:31:05 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x4M7V42U015994 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 22 May 2019 09:31:04 +0200 Received: from [139.25.69.232] (linux-ses-ext02.ppmd.siemens.net [139.25.69.232]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x4M7V3v3027531; Wed, 22 May 2019 09:31:04 +0200 Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage To: Jan Kiszka , "Maxim Yu. Osipov" , 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> <80d56fc5-00fa-5508-7fb1-976b4b5c61db@siemens.com> From: Claudius Heine Message-ID: Date: Wed, 22 May 2019 09:31:03 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <80d56fc5-00fa-5508-7fb1-976b4b5c61db@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: TqEDPIqpHc0t Hi Jan, On 22/05/2019 09.02, Jan Kiszka wrote: > 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. From dpkg-buildpackage(1): [...] -a, --host-arch architecture Specify the Debian architecture we build for (long option since dpkg 1.17.17). The architecture of the machine we build on is determined automatically, and is also the default for the host machine. [...] --target-arch architecture Specify the Debian architecture the binaries built will build for (since dpkg 1.17.17). The default value is the host machine. [...] Claudius > > Jan > -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de