[OE-core] [RFC] recipes-efl inside meta-oe or meta-efl next to meta-oe?

[Richard Purdie]

On Wed, 2011-03-23 at 16:42 +0100, Koen Kooi wrote:
> Op 23 mrt 2011, om 16:39 heeft Richard Purdie het volgende geschreven:
> 
> > On Wed, 2011-03-23 at 08:19 -0700, Khem Raj wrote:
> >> On Wed, Mar 23, 2011 at 4:49 AM, Koen Kooi <koen at dominion.thruhere.net> wrote:
> >>> Hi,
> >>> 
> >>> I'd like to import the EFL recipes Martin did from meta-shr into the meta-openembedded repo. Before I go bothering Martin about it, what would be the best place to put them?
> >>> 
> >>> Inside meta-oe:
> >>> 
> >>> meta-openembedded/
> >>>       meta-oe/
> >>>               recipes-efl
> >> 
> >> Can efl we layered directly on top of oe-core  ? i.e. without needing meta-oe
> >> in that case its better to be an independent layer. otherwise I would say put
> >> them under recipes-efl
> > 
> > I'd hope that it would be possible to run it on top of oe-core, at least
> > for its basic components. If its not possible, I'd like to understand
> > why so we can see if its possible to fix it.
> > 
> > Ultimately, we need to add some kind of layer dependency information
> > although we don't have an implementation of that yet.
> 
> I;m currently usng a low-tech README for that:
> 
> http://gitorious.org/angstrom/angstrom-layers/blobs/master/README
> 
> would be nice to come up with something machine parse-able.

That's the plan, have something in README's for now and then improve the
infrastructure over time to automate it.

We could define a simple convention of something like this in
layer.conf:

LAYERNAMES += "thislayername:<optionalversion>"

LAYERREQUIRES := '${@oe.util.layerrequirements(["layerA:versionA", "layerb:versionB"])}'

but its just random ideas off the top of my head at the moment!

Cheers,

Richard