public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage
Date: Thu, 23 May 2019 11:22:08 +0200	[thread overview]
Message-ID: <387dc456-dfa5-f403-4a0d-3bafffbaa00a@siemens.com> (raw)
In-Reply-To: <20190522191002.GB2441@yssyq.m.ilbers.de>

Hi Baurzhan,

On 22/05/2019 21.10, Baurzhan Ismagulov wrote:
> Hi,
> 
> what is the use case for such a change?

We are discussing here about possible ways to proceed, and AFAIK have 
not yet decided on it.

> 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.

The way isar currently uses the words 'host' and 'target' is in conflict 
which how gcc, Debian or the Yocto Project/OpenEmbedded uses them. This 
is a fact.

I think we have several ways to handle this issue:
1. Explain in the documentation front and center that we are using 
different definitions than most other prominent tools and projects.
2. Change our code to fit those other projects
3. Make up new words that are not used by those projects, but are 
comparatively descriptive.
4. Ignore that issue

Personally ignoring this issue would be the worst option. Since I 
guess/hope that there will be more people using isar in the future than 
currently are, so lowering the bar of entry by streamlining the use of 
technical terms should be desired.

regards,
Claudius

-- 
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

  reply	other threads:[~2019-05-23  9:22 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
2019-05-23  9:22                         ` Claudius Heine [this message]
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=387dc456-dfa5-f403-4a0d-3bafffbaa00a@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --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