From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage
Date: Wed, 22 May 2019 21:10:02 +0200 [thread overview]
Message-ID: <20190522191002.GB2441@yssyq.m.ilbers.de> (raw)
In-Reply-To: <cdd5166e-c445-8820-9944-e8366555fce8@siemens.com>
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_*'?
next prev parent reply other threads:[~2019-05-22 19:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 10:11 [PATCH v6 0/9] Cleanup rootfs creation claudius.heine.ext
2019-05-15 10:11 ` [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage claudius.heine.ext
2019-05-21 16:56 ` Jan Kiszka
2019-05-22 6:37 ` Claudius Heine
2019-05-22 6:55 ` Maxim Yu. Osipov
2019-05-22 7:02 ` Jan Kiszka
2019-05-22 7:31 ` Claudius Heine
2019-05-22 11:35 ` Jan Kiszka
2019-05-22 11:39 ` Claudius Heine
2019-05-22 12:15 ` Jan Kiszka
2019-05-22 12:50 ` Jan Kiszka
2019-05-22 13:37 ` Claudius Heine
2019-05-22 19:10 ` Baurzhan Ismagulov [this message]
2019-05-23 9:22 ` Claudius Heine
2019-05-15 10:11 ` [PATCH v6 2/9] isar-bootstrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-05-15 10:11 ` [PATCH v6 3/9] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-05-15 10:11 ` [PATCH v6 4/9] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-05-15 10:11 ` [PATCH v6 5/9] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-05-15 10:11 ` [PATCH v6 6/9] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-05-15 10:11 ` [PATCH v6 7/9] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-05-15 10:11 ` [PATCH v6 8/9] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-05-15 10:11 ` [PATCH v6 9/9] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext
2019-05-15 16:01 ` [PATCH v6 0/9] Cleanup rootfs creation Maxim Yu. Osipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190522191002.GB2441@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox