From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6690944878080163840 X-Received: by 2002:a19:2149:: with SMTP id h70mr43152962lfh.77.1558524906504; Wed, 22 May 2019 04:35:06 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:651a:: with SMTP id z26ls222930ljb.1.gmail; Wed, 22 May 2019 04:35:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqz/epr8KE6JjnBwQO8xeZX7B9R5V5tZp9m/qR0NqVpmD3y1tnXecHKvMSDG5tZDTUo7iG+Q X-Received: by 2002:a2e:9742:: with SMTP id f2mr11354123ljj.184.1558524905912; Wed, 22 May 2019 04:35:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558524905; cv=none; d=google.com; s=arc-20160816; b=Hk8gGrrysxg9L4E/8msyB9IJf7wy58fFQ+lvrxLUkEWNxN4af2PGDD/VejhHIBnB7R FP8qfVJ5BTVnMZUNLs+KbP3bPujco6fCj+hbgwGNV6/KRM+u6yNy3O3OlmT7opILcz/v XSFpGE05z9VjyrWofdUPZliG9++5nYB4lkkiRseC/uVo2sT6YDu2ls5YoWcxMnzUEV2B Cxh3tjOEJASLWM6GP77gbSaaw05fliM06PV6Uq1s9VZDTjjEZd6EjmdFkBOl9tbNtIer k1RsEVfvTsPOTjEp3EkqDrxI9kfedgi4OY5J5W2f2HtpjjJKzDEgT4c4kFQ3dLvyhSpZ dsLA== 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=ydy1ULrskwXjMsTT5tAdsNikUrf8o3xluzcBK9v7Jcg=; b=AaqBy1BN4XP/GPDkWlSdEQpdriCJw03uCX3OmasRjOvq7OLy5ppXptRl8+NZmtg+Md T49bWJFNJyKjpUX0dufT1l2EX+6/9j71e3ylIUl+lkA9SfhvKoo8buidCQ0nHhwwUz3l eHBDykc5HDPBQFRmN18u9lT88aMdwPEeGs2tiimL0PLVRf3jdDydOeJm1rLyqYHsl8vK TZBX/BYJCmxbmGfrVkMzx6FGgJzhm8pN2fHZzAgFtxiRPJiff/aAmqfcKq2vtWgKZxmI 1xaFXSVObGUPeOZTxSGeZwfjyDos1H1mCrrBnfydTwG3aB24YSZwJLaaNzdf4/ErruGf kG2A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 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 goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id p12si1808935ljh.5.2019.05.22.04.35.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 May 2019 04:35:05 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@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 goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x4MBZ4Ii013959 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 22 May 2019 13:35:04 +0200 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x4MBZ3W7018786; Wed, 22 May 2019 13:35:04 +0200 Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage To: Claudius Heine , "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: Jan Kiszka Message-ID: Date: Wed, 22 May 2019 13:35:04 +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: 8bit X-TUID: 5/yt7kGt3riC On 22.05.19 09:31, Claudius Heine wrote: > 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. > [...] > Then the current naming scheme is already accurate for Debian. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux