Re: [PATCH 4/6] Enable proper rebuilds on dependency changes

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2018-02-13 17:21, Jan Kiszka wrote:
> On 2018-02-13 14:03, Alexander Smirnov wrote:
>> On 02/12/2018 10:59 AM, Jan Kiszka wrote:
>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> Install a basichash as signature handler and set the stamp policy to
>>> full - and suddenly we get proper rebuilds of the image and all affected
>>> packages when some recipe down the dependency chain changed!
>>>
>>> We are using the legacy bitbake mechanism here as we do not have
>>> setscene machinery like OE. Still good enough for us.
>>>
>>
>> BTW: have you tried this? Two years ago I tried it in Yocto and it
>> didn't work properly, not all the dependents were rebuilt. If it works,
>> it's a very good feature!
> 
> Yes, I'm using it since this weekend for both Isar as well as
> jailhouse-images development, and it helped a lot already. The only
> limitation I found, but I do not remember right now if that isn't
> inherent to bitbake, is that it does not detect changes in files that
> the recipes carries in its SRC_URI (file://...). Then you need "-c
> clean" for the affected target - which now works as well.
> 

Found another issue, which worked surprisingly well so far despite being
fairly broken: do_setup_mounts is not re-run on rebuilds.

Should be fixable, specifically by avoiding to stamp it.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux