RE: [PATCH 0/6] imagetypes

["Schmidt, Adriaan" <adriaan.schmidt@siemens.com>]

Moessbauer, Felix (T CED SES-DE), 8. März 2022 15:10:
> Hi Adriaan,
> 
> > -----Original Message-----
> > From: isar-users@googlegroups.com <isar-users@googlegroups.com> On
> > Behalf Of Adriaan Schmidt
> > Sent: Thursday, February 10, 2022 7:25 AM
> > To: isar-users@googlegroups.com
> > Cc: Schmidt, Adriaan (T CED SES-DE) <adriaan.schmidt@siemens.com>
> > Subject: [PATCH 0/6] imagetypes
> >
> > This series introduces image types and conversions as known from OE.
> > The main motivation is to provide a more flexible way of generating and
> > processing images, without the need to insert custom tasks (e.g., currently
> > we have custom classes adding tasks for things like bz2 or xz compression
> of
> > images in several downstream layers).
> >
> > These patches have been tested on some of our layers, and also work with
> > some more "challenging" use cases like image-in-image recipes and custom
> > image types brought by layers.
> >
> > It's not perfect (e.g., documentation is still missing). Also I added just
> the
> > bare minimum of conversions, so there should probably be follow-ups for
> > additional compressions, or things like checksums, which can also be nicely
> > done with this.
> >
> > - p1 prepares by removing image-type-suffix from image build directories,
> >   which enables sharing of the completed rootfs across image types
> > - p2 refactors the SDK, and makes it an image feature instead of
> >   a separate recipe (has been discussed here a while ago)
> > - p3 does the actual work, but keeps all original files
> 
> At least for wic images, the bmap files are now written to
> `<image>.bmap.wic`, instead of `<image>.wic.bmap`.
> This is at least an API change and breaks some CI and flashing workflows.
> Don't know if that is intentional, but I prefer to have it like before.

That was not intentional, and will be corrected in the next update.
Adriaan

> Best regards,
> Felix
> 
> > - p4 moves code to different files
> > - p5 adapts meta-isar
> > - p6 removes IMAGE_FSTYPES as a dimension in multiconfig. Now that
> >   we can build multiple types from one rootfs, multconfig is
> >   just the wrong way of doing this (also been discussed here).