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

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

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.

> 
> Also do you know if this feature relies on DEPENDS variable? If so, we
> should keep this in mind with the idea to drop DEPENDS from recipes.

Don't ask me for the details, but it surely relies on task and target
dependencies, however they are calculated internally by bitbake.

Jan