From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Layer input
Date: Fri, 28 Jun 2013 12:07:58 +0100 [thread overview]
Message-ID: <1527627.N79fC8qGyO@helios> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF523E5@ORSMSX101.amr.corp.intel.com>
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
next prev parent reply other threads:[~2013-06-28 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 12:35 Layer input Rifenbark, Scott M
2013-06-25 12:42 ` Bruce Ashfield
2013-06-25 12:43 ` Rifenbark, Scott M
2013-06-25 18:06 ` Jerrod Peach
2013-06-27 7:41 ` Rifenbark, Scott M
2013-06-27 12:56 ` Jerrod Peach
2013-06-27 13:34 ` Rifenbark, Scott M
2013-06-27 21:02 ` Philip Balister
2013-06-28 6:13 ` Rifenbark, Scott M
2013-06-28 10:50 ` Rifenbark, Scott M
2013-06-28 11:07 ` Paul Eggleton [this message]
2013-06-28 11:22 ` Rifenbark, Scott M
2013-06-28 21:36 ` Khem Raj
2013-07-08 15:16 ` Paul Eggleton
2013-07-09 1:36 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1527627.N79fC8qGyO@helios \
--to=paul.eggleton@linux.intel.com \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.