RE: [RFC PATCH] image.bbclass: create separate task for creating reproducible image

[<Venkata.Pyla@toshiba-tsip.com>]

>-----Original Message-----
>From: Jan Kiszka <jan.kiszka@siemens.com>
>Sent: 27 February 2023 14:28
>To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>tsip.com>; isar-users@googlegroups.com
>Cc: felix.moessbauer@siemens.com; roberto.foglietta@gmail.com;
>henning.schild@siemens.com; hayashi kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ)
><kazuhiro3.hayashi@toshiba.co.jp>; dinesh kumar(ＴＳＩＰ TMIEC ODG
>Porting) <dinesh.kumar@toshiba-tsip.com>
>Subject: Re: [RFC PATCH] image.bbclass: create separate task for creating
>reproducible image
>
>On 27.02.23 08:50, venkata.pyla@toshiba-tsip.com wrote:
>> From: venkata pyla <venkata.pyla@toshiba-tsip.com>
>>
>> Currently the reproducible fix for setting same file timestamps across
>> builds is present in the function `do_rootfs_finalize` and this fix
>> may be skipped for the tasks that are added after this task or
>> `do_rootfs`  for e.g. in one of the child project(CIP) for swupdate
>> target it adds  additional task `do_generate_image_uuid` that is added
>> after `do_rootfs`  this task is updating some contents in the rootfs
>> which is skipping the  reproducible fix was applied in `do_rootfs_finalize`.
>>
>> For this reason a separate task `do_image_make_reproducible` is
>> created which should call before the final target image is created
>> [tar, wic, squashfs] so that it applies reproducible fixes just before
>> image creation.
>>
>> RFC:
>> In this patch I tried below dependency[1] for the function to solve
>> the above problem, it works now but I am not sure whether it guarantee
>> always this task `do_image_make_reproducible` will run just before
>> `do_image_[tar,wic,squashfs]` tasks or does it need more changes to
>> make it guarantee, any suggestions?
>>
>> [1] addtask image_make_reprodcible after do_rootfs before do_image
>>
>
>Isn't it possible to adjust isar-cip-core to perform do_generate_image_uuid
>before do_rootfs_finalize? Didn't check all details yet, just wondering.
>

Yeah that should be possible by changing its dependencies order,
but I just tried if it can be fixed in base recipes to address this problem commonly.

>Jan
>
>--
>Siemens AG, Technology
>Competence Center Embedded Linux