Re: [PATCH] cooker.py: Remove explicit build targets from the ignored list

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2013-05-31 at 11:32 -0500, Peter Seebach wrote:
> On Fri, 31 May 2013 08:29:43 +0100
> Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
> > I'm not sure this is the right thing to do, the reason being
> > determinism. I don't expect different results for X in the different
> > cases:
> > 
> > bitbake X Y
> > 
> > bitbake X
> > 
> > (assuming Y is ASSUME_PROVIDED)
> > 
> > For example, X will rebuild between these two commands since the sstate
> > and task checksums will be different between the two. This really needs
> > more thought to make a consistent user experience...
> 
> Hmm. I don't *normally* expect different results, but might if the first one
> produced a diagnostic: "Warning: Y is in ASSUME_PROVIDED. Rebuilding Y will
> produce different versions of anything which depends on Y."
> 
> Paul's suggestion that we just print a diagnostic for anything which is in
> both targets and ASSUME_PROVIDED might well do, too.

I'll certainly take a patch for that.

>  Although it might be nice
> to have a reasonably straight forward command-line way to express "no, really,
> I want you to build Y" which doesn't require config file action.

Agreed, however we need to get the user interaction right here.
Currently the user doesn't expect for example that the configuration
files change from under them. In future this may well be something we do
(along with informing the user what happened). Users tend not to read
information though :/.

Cheers,

Richard