Re: [PATCH 1/1] Re-add .wic prefix to deployed bmap file

["Roberto A. Foglietta" <roberto.foglietta@gmail.com>]

Il giorno dom 16 ott 2022 alle ore 05:58 MOESSBAUER, FELIX JONATHAN
<felix.moessbauer@siemens.com> ha scritto:
>
> > -----Original Message-----
> > From: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> > Sent: Sunday, October 16, 2022 1:10 AM
> > To: Schild, Henning (T CED SES-DE) <henning.schild@siemens.com>
> > Cc: Moessbauer, Felix Jonathan (T CED INW-CN)
> > <felix.moessbauer@siemens.com>; isar-users@googlegroups.com; Schmidt,
> > Adriaan (T CED SES-DE) <adriaan.schmidt@siemens.com>; Kiszka, Jan (T CED)
> > <jan.kiszka@siemens.com>
> > Subject: Re: [PATCH 1/1] Re-add .wic prefix to deployed bmap file
> >
> > Il giorno sab 15 ott 2022 alle ore 12:50 Henning Schild
> > <henning.schild@siemens.com> ha scritto:
> > >
> > > Am Sat, 15 Oct 2022 11:37:58 +0200
> > > schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
> > >
> > > > Il giorno ven 14 ott 2022 alle ore 13:51 Felix Moessbauer
> > > > <felix.moessbauer@siemens.com> ha scritto:
> > > > >
> > > > > This patch fixes a regression introduced in edc10d9.
> > > > > The bmap corresponds to the .wic file, hence it should also
> > > > > contain the .wic part of the filename.
> > > > >
> > > >
> > > > Thanks for this patch. However, the bmap tool works even if the name
> > > > of that file is changed.
> > >
> > > It sure does. But any scripting that comes after an isar build could
> > > get confused by the name change and not find the file. Like CD not
> > > even deploying it.
> >
> > just a matter of generalisation... :-)
>
> Too much generalization might just break things.
> The bmap file is specific to a block file, like the<image> .wic one.
> There might be other imagers or deployment formats, that use a different bmap.
> An with ISARs imagetypes, you can generate multiple image formats / types in a single run.
> Each of these could - in theory - have its own bmap, hence just appending .bmap to the image filename is not sufficient.
>

Thanks for the explanation. I wait for this patch to get accepted into
the 'next' and I will update the kas.yml with the new hash.

Best regards, R-