[yocto] Layer input

[Paul Eggleton]

On Friday 28 June 2013 10:50:01 Rifenbark, Scott M wrote:
> Here is the story on the relationship between the YP Metadata Layers as
> listed in the YP Source Repositories and the OpenEmbedded Metadata Index. 
> Functionally, the YP layers are a subset of the OE layers.  However, the YP
> layers are not a true subset of the OE layers.  The YP layers have many
> layers that do not appear in the OE index for one reason or another.  

I wouldn't say many, there are just a few exceptions. The way to look at it is 
the OE layer index is a central directory of layers that should be advertised, 
whereas what you see on git.yoctoproject.org is simply a listing of all of the 
repositories on git.yoctoproject.org, of which a subset are layers and a 
subset of those are current, maintained and should be promoted for people to 
use (and all of the latter should be in the OE layer index).

> Some YP layers are deprecated (e.g. meta-dlna), some should not be there and
> are being actively worked for removal or movement (e.g. poky-extras and
> yocto-docs).  Some are experimental layers (e.g. any layer that starts with
> "experimental"). And one is a contribution layer used by the Yocto Team
> (e.g. meta-intel-contrib).

FWIW, like the other contrib repos I think the latter is open access, anyone 
can get commit rights to facilitate sending pull requests.

> The text I create supporting this "layer" figure will describe this
> relationship so people will know from where existing layers originate.
> 
> I am deciding against adding more boxes to the already large figure and am
> going to retain just the large "Layers" box.  It will have supporting text
> that describes how a layer could be user-created, could originate from the
> YP Metadata Layers list, or could originate from the OpenEmbedded Metadata
> Index of layers.

Looking over the most recent version of this figure I'd suggest:

* conf/bblayers.conf in the distro layer shouldn't be there.

* The recipes-kernel in the distro layer should be dropped. I know we include 
linux-libc-headers-yocto in Poky but that is not typical.

* I think maybe like the other diagrams it would help if there were a different 
emphasis for items that are mandatory and items that are optional (e.g. 
bolding mandatory items or greying out optional items).

* Replace <mod_name> with <recipe>

* Replace <machine*> with <machine>

Cheers,
Paul



-- 

Paul Eggleton
Intel Open Source Technology Centre