RE: [PATCH 0/1] Remove hard-code distro name in the multistrap template

["Hombourger, Cedric" <Cedric_Hombourger@mentor.com>]

Hi Alex,

Sorry for the delayed response, last few days were hectic over here :)

1. Well if you have a layer setting DEBDISTRONAME then the dpkg-base class uses the user-defined name and the buildchroot class will fail to fetch custom packages you may have as build dependencies
2. I don't think it does, isar-image-base.bb also does a subst: -e 's|##ISAR_DISTRO_SUITE##|${DEBDISTRONAME}|g'

Does that make sense / help?

Cedric

-----Original Message-----
From: Alexander Smirnov [mailto:asmirnov@ilbers.de] 
Sent: Friday, March 2, 2018 1:35 PM
To: Hombourger, Cedric <Cedric_Hombourger@mentor.com>; isar-users@googlegroups.com
Subject: Re: [PATCH 0/1] Remove hard-code distro name in the multistrap template

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