From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Samuel Stirtzel <s.stirtzel@googlemail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Questions about the layer structure in OpenEmbedded-Core
Date: Fri, 12 Aug 2011 10:08:03 +0100 [thread overview]
Message-ID: <201108121008.03554.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <CAGiJk9fq+p3LcBOOz=V+_kprRppAOR-nOAOW6tgK3zwE78Skwg@mail.gmail.com>
On Friday 12 August 2011 07:17:52 Samuel Stirtzel wrote:
> lately I looked a bit into the structure of OE-Core and found pages
> like: http://www.yoctoproject.org/projects/openembedded-core, and
> http://openembedded.org/index.php/LayerIndex
>
> 1. question: Are these informations reliable (the layer index page
> seems outdated).
I wrote both of these with input from the community recently, so they should
be fairly reliable and up-to-date - was there something missing that you
noticed? Suggestions welcome.
> 2.: Currently the "UI layer" seems to be contained in
> meta-openembedded, so is this _the_ layer for UI and windowmanager
> recipes or is this a subject to change?
There are several different UIs available. OE-core provides Sato (mainly for
testing); the meta-openembedded repository contains several layers that
provide some more (GNOME, XFCE, etc.)
> 3.: The commercial layer is nowhere found, what are the plans for this
> layer, or was this just an idea?
As Denys mentioned this sort of thing is (or is expected to be) provided by
multiple OSVs.
> 4.: In which layer would distributions fit in the graphic?
I would imagine they would take the place of the commercial layer - after all,
both would be providing the same sorts of "policy" type metadata.
> 5.: Is something important missing / wrong in my graphic (other than
> the distro stuff)?
It looks good, but I'm not sure that you'd expect to be mixing all of these
layers together in one configuration; e.g. the commercial layer / distro
layers.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-08-12 9:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 6:17 Questions about the layer structure in OpenEmbedded-Core Samuel Stirtzel
2011-08-12 6:27 ` Denys Dmytriyenko
2011-08-12 7:30 ` Samuel Stirtzel
2011-08-12 7:42 ` Koen Kooi
2011-08-12 8:50 ` Samuel Stirtzel
2011-08-12 9:08 ` Paul Eggleton [this message]
[not found] ` <CAGiJk9dGQ5N0xd+L81Bit-jp4YDYPwSBjNvn5_io38vyH2nREg@mail.gmail.com>
2011-08-12 10:47 ` Paul Eggleton
2011-08-12 11:59 ` George C. Huntington, III
2011-08-15 9:06 ` Samuel Stirtzel
2011-08-12 12:07 ` Koen Kooi
2011-08-12 13:16 ` Paul Eggleton
2011-08-12 13:18 ` Philip Balister
2011-08-15 9:06 ` Samuel Stirtzel
2011-08-15 9:19 ` Paul Eggleton
2011-08-16 6:51 ` Samuel Stirtzel
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=201108121008.03554.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=s.stirtzel@googlemail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox