[bitbake-devel] [PATCH 1/1] cooker.py: Remove explicit build targets from the ignored list

[Chris Larson]

On Thu, Aug 9, 2012 at 10:44 AM, Peter Seebach
<peter.seebach at windriver.com> wrote:
> On Thu, 9 Aug 2012 18:30:57 +0100
> Paul Eggleton <paul.eggleton at linux.intel.com> wrote:
>
>> I'd rather we not change it to behave this way - the better approach
>> would seem to me to be to just print a warning that the requested
>> target is in ASSUME_PROVIDED and then not do anything else; if the
>> user really wants to build the thing they can just remove it from
>> ASSUME_PROVIDED.
>
> Removing things from ASSUME_PROVIDED can be a bit tricky, because they
> can come from more than one place. And it may not be easy to see where
> they came from. (In my most convenient build, there are at least two
> files setting ASSUME_PROVIDED.)

For what it's worth, I agree with Peter's approach on this. The user
should always be able to override assumptions. Explicit should win.
Technically variables can be explicitly set by the user as well, but
generally speaking I think we have always interpreted the command-line
as overriding the metadata when appropriate. Consider BBPKGS, which is
a list of providers to build if and only if the user doesn't specify
any.
-- 
Christopher Larson