[poky] sstate status

[Tian, Kevin]

>From: Paul Eggleton [mailto:paul.eggleton at linux.intel.com]
>Sent: Wednesday, December 08, 2010 7:32 PM
>
>On Wednesday 08 December 2010 11:22:40 Tian, Kevin wrote:
>> The weird behavior I saw yesterday is still there: lots of recipes (such as gzip-native) are
>> rebuilt when I build poky-image-minimal, which however finally ends up to override my
>> sstate cache with same checksums.
>>
>> If I end the build when it finished setscene stage, and then simply build tasks in the
>runqueue
>> such as gzip-native, git-native, . It just succeeds by reusing sstate package.
>>
>> Quite strange... Still look into it now.
>
>Oops, it appears that I pushed the wrong branch to paule/sstate yesterday. I've re-pushed
>a new one which actually includes the variable whitelisting changes.

Do we still need those variable whitelisting changes? Based on original branch you pushed
(basically RP's branch rebased on master imo), I think it basically works at least for a single
recipe build though above weird issue exists for image build.

Of course we need keep some bitbake specific variables in whitelist, such as DATE, TIME and
several others you added in last commit.

On the other hand, did you observe my issue on this new push? I want to understand its
root cause, which is really funny. 

>
>Sorry about that!
>

No problem. :-)

Thanks
Kevin