All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stewart, David C" <david.c.stewart@intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Documenting YP Development Environment in more detail - user configuration
Date: Tue, 9 Jul 2013 13:51:06 +0000	[thread overview]
Message-ID: <CE016295.3C663%david.c.stewart@intel.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF5AD30@ORSMSX101.amr.corp.intel.com>



On 7/8/13 10:54 PM, "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
wrote:

>Here is a link to draft section on the user configuration block of the YP
>Development Environment work.  Check this out and provide feedback for
>appropriate level of detail, usefulness, missing info, ect.  This draft
>section, once we settle on it, will set the tone and level for the
>remaining detailed sections that make up the general environment diagram.
> 
>
>http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#a-closer-l
>ook-at-the-yocto-project-development-environment

I think it will look really good.

Would it make sense to adopt some kind of notation for when a directory is
a "source" vs "destination" type directory? For example, in the diagram
you have there, maybe color the source and destination directory boxes
differently or use hashed lines vs solid? Not sure it will be clear or
confusing once you get into more examples.

Also, it's a nit, but I think oe-init-build-env only creates the Build
Directory if it doesn't already exist.

>
>Thanks, 
>Scott
>
>>-----Original Message-----
>>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>>bounces@yoctoproject.org] On Behalf Of Burton, Ross
>>Sent: Tuesday, June 25, 2013 2:55 AM
>>To: Philip Balister
>>Cc: yocto@yoctoproject.org
>>Subject: Re: [yocto] Documenting YP Development Environment in more
>>detail - user configuration
>>
>>On 25 June 2013 01:39, Philip Balister <philip@balister.org> wrote:
>>> 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.
>>
>>Is there such a thing as a "typical" use of oe-core + layers?  Poky
>>uses a custom tool (combo-layer, in oe-core/scripts) to merge the
>>layers into a single repo.  You could also use git submodules to make
>>a single repo (such as Guacamayo), or git subtree merges, or use repo
>>(gumstix), or have a script that manages the fetching of multiple
>>layers (Angstrom).
>>
>>Ross
>>_______________________________________________
>>yocto mailing list
>>yocto@yoctoproject.org
>>https://lists.yoctoproject.org/listinfo/yocto



  reply	other threads:[~2013-07-09 13:51 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
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 [this message]
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=CE016295.3C663%david.c.stewart@intel.com \
    --to=david.c.stewart@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.