From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6690944878080163840 X-Received: by 2002:a5d:54c9:: with SMTP id x9mr38084322wrv.266.1558552210386; Wed, 22 May 2019 12:10:10 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:600c:28a:: with SMTP id 10ls1028066wmk.3.canary-gmail; Wed, 22 May 2019 12:10:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqzWxCr7sSbheNcVGtoiiX8YNP9otpZjlp82f0uh4pkeXuuG16Lsbb7WJgOAwkDH7GSfJM2o X-Received: by 2002:a1c:c582:: with SMTP id v124mr9121207wmf.111.1558552209935; Wed, 22 May 2019 12:10:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558552209; cv=none; d=google.com; s=arc-20160816; b=H4VVLlnCf+yx5kIuKj/i7hJocBkJcvt6tDKT5B6lXh7coVamfIyRgK22zIo/15PoWx bWP0Hm++xrfS7UeMaaog8qTlom1mp/eUo+QOJaV/N6cObf0ifEH87f7bat6gZqwjA6ln twlFua49S/fc8DEW/TRxar/7WyxvIpi0ZC5SgBekhk9i+/U8TS7E4HZKzQ5cpwOslh44 Vu2oimIrCX3F6NxvCebJgVgvRD1mdjM+FhqhuFf/Df2yoLOr+2BNdmexab0OzcTmYeHY B0x8LxGYhH0403PNpSPHZewYGmr9O0DCx1CBtXT4NnyOTawzQq8fdEmdq/TkM1XyakbV UfUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=XVsLRcEOqGZ6DSXRboDN4gZFXk2lwkSaiNwD8ia35+U=; b=nAu1TdLH6g9cjcw08+tOQ+QvqZ/a3hZYYZsPLtFTiRBWkx58gZOghdLJXG4wa0tnZ0 bWDANs+rG9YzhPe5f0OgJ92GdF2fw9a81kl3ijCco2Di3CIIYLwHj9DZZpBF0seO0Jj5 HUzyXUsWTcrw8lUy6H93y4VCGbU4SAkyADyTzz1ti5pXCLvBidpoI4uAVXAWdXKoTj3e 2eiP0OzTVW+R2bjaLGnK3oqH+2XtPZZYWDdiZkFBeDMmtj9a/w4E755pehT5KMFwTOwa T02E5hqyFWk/lyQzvqM/Nn+/3ffprH6g8shcY1EMVu48MijgrEAZ3ZKQ989m5/rOfxTp q14Q== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id p18si419345wmh.1.2019.05.22.12.10.09 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 22 May 2019 12:10:09 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (dslb-002-200-058-019.002.200.pools.vodafone-ip.de [2.200.58.19]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x4MJA8h7006078 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 22 May 2019 21:10:09 +0200 Date: Wed, 22 May 2019 21:10:02 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage Message-ID: <20190522191002.GB2441@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com References: <3745f4ba-e3c9-4d59-22e4-9746c6497f6b@siemens.com> <80d56fc5-00fa-5508-7fb1-976b4b5c61db@siemens.com> <514b7749-f950-ec44-b5a2-affcbfb91e6d@siemens.com> <0a86b0e8-8b57-d2c7-998c-d099952af86b@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: /1JBRZqvIbw5 Hi, what is the use case for such a change? The system works. The names are intuitive for the users. If anything is not clear, we can define the terms in the docs. Binutils and gcc are more complex systems that require (a very non-intuitive) triplet; we don't. Having "host" and "target" in the directory names is also convenient for the user. Therefore, I'm not in favor of this change. With kind regards, Baurzhan. On Wed, May 22, 2019 at 03:37:37PM +0200, Claudius Heine wrote: > With my patchsets we could probably even drop 'build', 'host' and 'target' > from the recipes all together and just go for the build host tupel. For > instance: > > "buildchroot-host-amd64-arm" -> "buildchroot-amd64-arm" > "buildchroot-target-arm" -> "buildchroot-arm" > "isar-bootstrap-host-amd64-arm" -> "isar-bootstrap-amd64-arm" > "isar-bootstrap-target-arm" -> "isar-bootstrap-arm" > > That would only affect the PN variable in those recipes, the file names > would probably be 'isar-bootstrap-build.bb'/'isar-bootstrap-native' (which > is what yocto is using to avoid 'build') and > 'isar-bootstrap-host.bb'/'isar-bootstrap.bb'. > > For the variables just renaming 'HOST_*' stuff to 'BUILD_*' stuff would be > ok, but maybe a bit confusing, because 'build' might be a bit vague there. > How about 'NATIVE_*'?