From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6690944878080163840 X-Received: by 2002:a1c:f311:: with SMTP id q17mr7268956wmq.144.1558525177603; Wed, 22 May 2019 04:39:37 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:600c:148:: with SMTP id w8ls597798wmm.3.gmail; Wed, 22 May 2019 04:39:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqwShoNs+3RgWKDeXLXIZie3cMwQKf6flAWOgxOVOmf8PYgxEbONMV790YPp2nXX8RjdPBAq X-Received: by 2002:a7b:c744:: with SMTP id w4mr7520299wmk.116.1558525177205; Wed, 22 May 2019 04:39:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558525177; cv=none; d=google.com; s=arc-20160816; b=qPKIUDWN+iNl0WT+kUcQ7gsqDSqyCmxpSgSw62kXrmjB9eU4VfmNNY2CR2/cdAsNrN YG5sW6Bb3e+0aWphZdK7NVVIfA34K3jiIlu9fS1KVZKUpjeDuFQw0CQ275xdD8ZVG4Wm 070ArivqdRBRhlkvAQDfxvSh7JQFhT0mou2+KC/L0RRrRapy9KgwXX3zfiqW/rbGDmXq nDbiO8iZyXSCQdHd3PhEVgzw1ml23Z6fTOLIGDN+9446S6M0wVwfdHDYJoHKnndF+MW1 gjXm4+qTEkn5ajFaABsLQO3Kag/g3CH5x10i4U4qALD5yO1ISYxOhfTvHAfUlWA3yYps j8dw== 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=h8T3jJXn6Ct8hqfzdySb2woQbKA45wBxU1o9Ph2JfSY=; b=Wo3QSENT49hP1dd8wBgufGjAnM2AzayRpSXznME/0NVlTXsMvTIpaF9TW0/+jBCDr4 vtKt7am6jgKeUDpkg3E/qOmGQb/waXXo/rUEupxh0C42xrv9Fo6XVcAJBi9TyxYd+p/Z diaTaUmaKJFsQgpvKKKHeq1vAVkoo3z9Mtb0SdDfkXlhDPItqTDwL8Dy/3bsnKr0Ni1t aTLuQSK3ezjB9yxBhaI4CfcZBNpnV5VEVy56QEHIYSf9v0Ue6+PBu2qbd0F1dRw4DtVP LJvpsPkb+O/IP78g9Q8fBXCi9359bc/C1FMrgz1n09k8dcDwnbjeNzfq3xPtxoZZMrbd GnBw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 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 thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id q11si616139wrj.2.2019.05.22.04.39.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 May 2019 04:39:37 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 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 thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x4MBdaa3018196 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 22 May 2019 13:39:36 +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 x4MBdawv029858; Wed, 22 May 2019 13:39:36 +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: <514b7749-f950-ec44-b5a2-affcbfb91e6d@siemens.com> Date: Wed, 22 May 2019 13:39:36 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: W7kA+6JVaLSh On 22/05/2019 13.35, Jan Kiszka wrote: > 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. No? That is not how I read that documentation. "Host" is what we build for and 'Target' is what the binaries we build generate code for (which makes only sense for compilers) 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