All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Jeff Osier-Mixon <jefro@jefro.net>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Documenting YP Development Environment in more detail - user configuration
Date: Mon, 24 Jun 2013 20:39:08 -0400	[thread overview]
Message-ID: <51C8E6AC.5000704@balister.org> (raw)
In-Reply-To: <CA+YB3rbnUOssFc-w5Ak-X_rVPqhJnkJ+NiWEyJDJXL61gGJ0Gg@mail.gmail.com>

On 06/24/2013 02:37 PM, Jeff Osier-Mixon wrote:
> On Mon, Jun 24, 2013 at 11:25 AM, Philip Balister <philip@balister.org> wrote:
>> Showing how Poky (the reference distribution) is built would be a nice
>> way to introduce people to building their own custom distributions using
>> OpenEmbedded.
> 
> Totally agree, but I would relegate that to a separate effort. The
> main problem with diagrams like this is trying to squeeze in too much
> information in order to preserve completeness, at the expense of
> clarity. It would be more ideal to start with a very simple diagram,
> then move on to other diagrams to zoom in on pertinent detail. It is a
> delicate balancing act. In this case, I would say to put "how Poky is
> built" into the 3rd or 4th diagram in a series.
> 
> I'm glad to see this conversation happening!

I totally agree we drifted way beyond the initial discussion of the
figure. The key thought here is understanding how Poky differs from a
typical use of oe-core + other layers.

Philip


  reply	other threads:[~2013-06-25  0:39 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
2013-06-24 18:37                 ` Jeff Osier-Mixon
2013-06-25  0:39                   ` Philip Balister [this message]
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=51C8E6AC.5000704@balister.org \
    --to=philip@balister.org \
    --cc=jefro@jefro.net \
    --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.