[OE-core] [RFC] One shared state reuse solution

[Chris Larson]

On Fri, Mar 30, 2012 at 3:02 PM, Koen Kooi <koen at dominion.thruhere.net> wrote:
> Op 30 mrt. 2012, om 14:54 heeft Chris Larson het volgende geschreven:

>> I'm looking for questions, comments, testers, and in particular,
>> thoughts on whether this will meet the needs of others with similar
>> requirements (e.g. others shipping metadata with associated shared
>> state).
>
> This is not strictly related to your patchset, but has anyone thought about license based blacklisting of sstate? I can imagine that an autobuilder will build everything, includes things like evil 3d drivers, but no want anyone to access the sstate for those builds.

Oh, that's a very good point. I hadn't considered that aspect. I
haven't seen any implementation in that regard (actually, I have no
idea how one goes about disabling sstate period -- it'd be nice if
there was an easy variable rather than having to go deleting tasks and
the like).
-- 
Christopher Larson