[oe] overriding tasks with EXPORT_FUNCTIONS

[Paul Eggleton]

Hi Trevor,

On Tuesday 22 July 2014 09:19:05 Trevor Woerner wrote:
> On 07/14/14 08:26, Paul Eggleton wrote:
> > Unfortunately as far as the BitBake manual is concerned, it pretty
> > much has to be abstract. Remember that there are no base
> > implementations of any task functions in BitBake itself; the ones you
> > refer to are in OE's base.bbclass.
> 
> In reality there are only about 2 people on the whole planet for whom
> that distinction is important :-)

I see where you're coming from, but we want BitBake to remain usable 
independently, and that means it affects anyone who works on BitBake not just 
the few that do use it independently. That also means that the documentation 
should stand on its own - it *can* use examples from the OE metadata, but it 
has to be clear that it is an example from OE, and it should describe the 
example fully - it can't blur the lines between OE and BitBake; if you start 
assuming OE functionality when documenting BitBake, that's exactly what you'll 
be doing.

> For the rest of us, it would be nice if there was some middle ground
> from which a document could be written that treated these two entities
> as one; 

That's exactly what the Yocto Project manuals do. They refer to the BitBake 
manual where we want to describe some syntax or other fundamental BitBake 
concept in more detail. However, it's OK to have duplication between the 
BitBake manual and the Yocto Project manuals where we can add more relevant 
detail on the Yocto Project side - but I'd rather not see complete 
duplication.

> at least up until such a time as some other project comes along
> and uses bitbake for something other than OE/Yocto :-D

FWIW I think there are other projects already. We don't hear about them a lot, 
but they have come up from time to time.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre