From: Philip Balister <philip@balister.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Documenting YP Development Environment in more detail - user configuration
Date: Mon, 24 Jun 2013 14:25:38 -0400 [thread overview]
Message-ID: <51C88F22.6030605@balister.org> (raw)
In-Reply-To: <CAJTo0LbwiP-WR1uetxLgMxC0beO198kg-ubO_oWd85JRv4eaqg@mail.gmail.com>
On 06/24/2013 12:59 PM, Burton, Ross wrote:
> On 24 June 2013 17:55, Philip Balister <philip@balister.org> wrote:
>> Explaining how poky is built up from oe-core + meta-yocto +
>> meta-yocto-bsp + some other stuff would be really helpful in reducing
>> confusion over what all the pieces are and where they come from.
>
> Agreed - explaining clearly that Poky is mostly an aggregation of
> existing repositories and not actually canonical upstream for anything
> is probably a good move, as this is clearly misunderstood by many
> people.
Showing how Poky (the reference distribution) is built would be a nice
way to introduce people to building their own custom distributions using
OpenEmbedded.
Philip
next prev parent reply other threads:[~2013-06-24 18:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 3:52 Documenting YP Development Environment in more detail - user configuration Rifenbark, Scott M
2013-06-24 12:59 ` Jerrod Peach
2013-06-24 14:08 ` Burton, Ross
2013-06-24 14:12 ` Rifenbark, Scott M
2013-06-24 13:15 ` Philip Balister
2013-06-24 14:27 ` Rifenbark, Scott M
2013-06-24 14:47 ` Robert P. J. Day
2013-06-24 14:57 ` Burton, Ross
2013-06-24 15:08 ` Rifenbark, Scott M
2013-06-24 16:55 ` Philip Balister
2013-06-24 16:59 ` Burton, Ross
2013-06-24 18:25 ` Philip Balister [this message]
2013-06-24 18:37 ` Jeff Osier-Mixon
2013-06-25 0:39 ` Philip Balister
2013-06-25 4:58 ` Rifenbark, Scott M
2013-06-25 9:54 ` Burton, Ross
2013-07-09 5:54 ` Rifenbark, Scott M
2013-07-09 13:51 ` Stewart, David C
2013-07-09 14:23 ` Rifenbark, Scott M
2013-06-24 17:00 ` Rifenbark, Scott M
2013-06-28 19:58 ` Khem Raj
2013-06-29 4:50 ` Rifenbark, Scott M
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=51C88F22.6030605@balister.org \
--to=philip@balister.org \
--cc=ross.burton@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.