[poky] sstate status

Tian, Kevin kevin.tian at intel.com
Tue Dec 7 16:40:59 PST 2010


>From: Richard Purdie [mailto:rpurdie at linux.intel.com]
>Sent: Tuesday, December 07, 2010 11:03 PM
>
>On Tue, 2010-12-07 at 15:46 +0800, Tian, Kevin wrote:
>> >From: Richard Purdie [mailto:rpurdie at linux.intel.com]
>
>> >http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/commit/?h=tk/sstate&id=0a4c46dc
>2c1
>> >22ef5c1057380e79b75e302583b4a, siggen.py: fix python error when comparing sstate
>> >generated from different srcpath
>> >
>> >I understand the need for this but I don't like the implementation :)
>> >
>> >We can't use OEROOT here as its not a standard variable and is
>> >deprecated. I was initially thinking POKYBASE but that isn't right
>> >either in bitbake. Hmm.
>>
>> Could you elaborate why POKYBASE can't be used too? Because LAYERDIR is a
>> one-time expansion action? If we're sure that POKYBASE is expanded before
>> base signature generation, then it could work.
>
>POKYBASE is poky specific and not a bitbake variable. Using it in
>generic bitbake code is therefore a layer violation.

Got it.

>
>> >Chris, any suggestions? I'm actually struggling a bit to come up with a
>> >variable that represents a "head" of the metadata :/. Perhaps filename
>> >would be enough in this case?
>> >
>> >I'd also suggest we remove this path when we save the siginfo file, not
>> >when we load it and do the comparison.
>>
>> Yes, that's a better approach. I'll go that approach.
>
>Thanks, I'll wait for an updated patch.
>
>> That's my intention too. Above logic is to filter out native/cross dependencies.
>> If we do that filter for native/cross tasks too, that means all dependencies
>> would be wiped out which is not what we want since they all fall into the
>> match group. That's why I add the initial condition to restrict the filtering on
>> on target packages. :-)
>
>Ok, this makes sense. I merged it after adding in some comments to the
>code.
>
>I've asked Paul to pull together a branch with all the changes in for
>sstate and see how we stand.
>
>

OK, I'll wait for that new branch to have another try.

Thanks
Kevin


More information about the poky mailing list