Re: [PATCH] sstate: Make image cache imagetype-specific

[Anton Mikanovich <amikan@ilbers.de>]

15.12.2021 17:33, Schmidt, Adriaan wrote:
> Actually, now that IMAGE_FSTYPES supports generating multiple images
> with different types at once, multiconfig is the wrong way to go in
> this scenario.
>
> When creating the same two images via IMAGE_FSTYPES="targz-img cpiogz-img"
> there is no problem, and we can then even go one step further and
> remove the ${IMAGE_SUFFIX} completely.
> Eventually, this will enable better sharing (and caching), e.g., in this
> case both images are built from the same rootfs, which is what is
> stored in the sstate-cache.
>
> Also, when removing IMAGE_SUFFIX, the task-once-stamp logic from isar-events
> will warn that something is wrong in case IMAGE_FSTYPES is set in
> multiconfig (which is exactly what we want):
>
> ERROR: Detect multiple executions of do_image in /work/build/tmp/work/debian-buster-amd64/isar-image-base-qemuamd64/1.0-r0
> ERROR: Rerun a clean build with empty STAMPCLEAN and compare the sigdata files
>
> Adriaan

Making different image types share the same rootfs sounds really good, 
but its separation was compelled.
Some architectural changed will be needed to make it work.

-- 
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov