Re: [PATCH v12 0/3] Move kernel artifacts deployment from image recipe

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 07.07.26 11:52, 'Quirin Gylstorff' via isar-users wrote:
> 
> 
> On 7/3/26 5:08 PM, Anton Mikanovich wrote:
>> Image task "do_copy_boot_files" is used to deploy kernel and
>> devicetree binaries to deploy directory.
>>
>> When different images for the same target are built (e.g., "-base" and
>> "-debug") in parallel, this causes issues with DTB deployment since
>> they have no any image_name-specific stuff in the path, unlike kernel
>> and initrd.
>>
>> Here we move DTB deployment to the kernel recipe (for both distro and
>> custom kernel recipes), where DTBs and kernel image are extracted from
>> the kernel package.
>> For the distro kernels it means we install its deb into the schroot to
>> obtain the real artifacts from the filesystem.
>>
>> To keep the same artifacts path as before "do_copy_boot_files" task is
>> now searching for the artifacts and create per-image symlinks.
>> In case any naming conflicts (like dtbs with the same name from
>> different kernels) the latest built dtb will be pointing by the
>> symlink, while both will be deployed to different subdirs without
>> conflicting and stay untouched.
>> This symlink creation is done in the same way as artifacts conficts are
>> handled by Yocto.
>>
>> The case when different distros (e.g., bullseye/bookworm) are using the
>> same name for DTB binaries is covered by the patch 2. It also covers
>> the case when image uses different kernel suffix (e.g., "realtime"
>> option for the kernel in some downstreams).
> 
> In my option we should go back to the design board as multiconfig and
> Debian are in conflict in this case.
> 
> We should decide what we want to support with  multiconfigs and what not.
> 
> The technical implementation should come afterwards.
> 
> We should also disallow some of the possible use cases of multiconfig.
> 

Ack. Given that only Isar upstream was apparently bitten by this so far,
none of our various user layers, it is really questionable how much
value we would add, compared to the complications we are causing, both
to our users as well as to Isar itself.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/1c64b051-9e6c-4891-904b-8efc578dd904%40siemens.com.