From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
<isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] buildchroot: remove hard-coded distro names in the multistrap template
Date: Mon, 25 Feb 2019 17:03:02 +0100 [thread overview]
Message-ID: <20190225170302.56f0fef2@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <554bc1a2-8772-5ca3-eb92-d310ce09b4ff@siemens.com>
Am Fri, 22 Feb 2019 11:32:57 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> On 22.02.19 11:26, [ext] Henning Schild wrote:
> > Hi,
> >
> > unfortunately Isar is pretty inconsistent with debian naming.
> > "Debian" is a distro, like "ubuntu" or "mint". "stretch" and
> > "buster" are suites ...
> >
> > suite=distro is wrong
> >
> > Please choose another name for that variable. One point less to
> > clean up when setting things straight.
> >
> > Henning
> >
> > Am Wed, 21 Feb 2018 13:19:24 +0000
> > schrieb Cedric Hombourger <Cedric_Hombourger@mentor.com>:
>
> Were you on a time ride, Henning? :)
Oh, i guess Feb looked ok ;). I recently had to change mail clients,
and thunderbird seriously messes with your mails if you just use it
once a quarter....
Henning
> Jan
>
> >
> >> The multistrap configuration template assumes the distribution
> >> will be "isar"; this may however be changed via the DEBDISTRONAME
> >> variable. Add yet another variable substitution to the template
> >> processing code.
> >>
> >> Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> >> ---
> >> meta/recipes-devtools/buildchroot/buildchroot.bb | 1 +
> >> meta/recipes-devtools/buildchroot/files/multistrap.conf.in | 2 +-
> >> 2 files changed, 2 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/meta/recipes-devtools/buildchroot/buildchroot.bb
> >> b/meta/recipes-devtools/buildchroot/buildchroot.bb index
> >> 520daf9..12577c7 100644 ---
> >> a/meta/recipes-devtools/buildchroot/buildchroot.bb +++
> >> b/meta/recipes-devtools/buildchroot/buildchroot.bb @@ -60,6 +60,7
> >> @@ do_build() { -e
> >> 's|##DISTRO_APT_SOURCE_SEC##|${DISTRO_APT_SOURCE_SEC}|g' \ -e
> >> 's|##DISTRO_SUITE##|${DISTRO_SUITE}|g' \ -e
> >> 's|##DISTRO_COMPONENTS##|${DISTRO_COMPONENTS}|g' \
> >> + -e 's|##DEBDISTRONAME##|${DEBDISTRONAME}|g' \
> >> -e
> >> 's|##CONFIG_SCRIPT##|./'"$WORKDIR_REL"'/configscript.sh|g' \ -e
> >> 's|##SETUP_SCRIPT##|./'"$WORKDIR_REL"'/setup.sh|g' \ -e
> >> 's|##DIR_HOOKS##|./'"$WORKDIR_REL"'/hooks_multistrap|g' \ diff
> >> --git a/meta/recipes-devtools/buildchroot/files/multistrap.conf.in
> >> b/meta/recipes-devtools/buildchroot/files/multistrap.conf.in index
> >> 480a4b8..ee0ea09 100644 ---
> >> a/meta/recipes-devtools/buildchroot/files/multistrap.conf.in +++
> >> b/meta/recipes-devtools/buildchroot/files/multistrap.conf.in @@
> >> -32,6 +32,6 @@ omitdebsrc=true [isar-apt]
> >> source=file:///isar-apt
> >> -suite=isar
> >> +suite=##DEBDISTRONAME##
> >> components=main
> >> omitdebsrc=true
> >
>
next prev parent reply other threads:[~2019-02-25 16:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 13:19 [PATCH 0/1] Remove hard-code distro name " Cedric Hombourger
2018-02-21 13:19 ` [PATCH 1/1] buildchroot: remove hard-coded distro names " Cedric Hombourger
2019-02-22 10:26 ` Henning Schild
2019-02-22 10:32 ` Jan Kiszka
2019-02-25 16:03 ` Henning Schild [this message]
2018-02-21 15:30 ` [PATCH 0/1] Remove hard-code distro name " Claudius Heine
2018-02-21 15:51 ` Hombourger, Cedric
2018-02-21 16:10 ` Claudius Heine
2018-03-02 12:34 ` Alexander Smirnov
2018-03-07 11:24 ` Hombourger, Cedric
2018-03-15 13:59 ` Alexander Smirnov
2018-04-04 6:25 ` chombourger
2018-04-04 10:43 ` Jan Kiszka
2018-04-04 10:49 ` Cedric Hombourger
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=20190225170302.56f0fef2@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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