From: Alexander Smirnov <asmirnov@ilbers.de>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 0/1] Remove hard-code distro name in the multistrap template
Date: Fri, 2 Mar 2018 15:34:49 +0300 [thread overview]
Message-ID: <9aa144b7-2c7e-af49-abf9-7a463afae24d@ilbers.de> (raw)
In-Reply-To: <20180221131924.4744-1-Cedric_Hombourger@mentor.com>
Hi,
On 02/21/2018 04:19 PM, Cedric Hombourger wrote:
> As users may define their own distro name, the multistrap configuration template
> we provide should not have it hard-coded to "isar" but use whatever DEBDISTRONAME
> setting we receive. Failure to do will result in fetch failures from the isar-apt
> source feed.
I have two questions here:
1. What is the user impact to define distro name *in* buildchroot? This
should be absolutely transparent for user, this apt is used only to
install deps for building new packages.
2. Why the distro name for image multistrap remains Isar then?
Alex
next prev parent reply other threads:[~2018-03-02 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 13:19 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
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 [this message]
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=9aa144b7-2c7e-af49-abf9-7a463afae24d@ilbers.de \
--to=asmirnov@ilbers.de \
--cc=Cedric_Hombourger@mentor.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