All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: oe-core cleanup...
Date: Thu, 3 Mar 2011 07:49:37 -0700	[thread overview]
Message-ID: <4D6FAA81.1020306@mentor.com> (raw)
In-Reply-To: <4D6FA92C.5010507@windriver.com>

On 03/03/2011 07:43 AM, Mark Hatle wrote:
> On 3/3/11 6:10 AM, Richard Purdie wrote:
>> I'd really at least like the TSC members to comment on those different
>> pieces. I've already seen Chris comment that "poky-init-build-env"
>> shouldn't be in the core for example. What about the rest of the scripts
>> directory?
>
> I think they should be in oe-core, and specifically labeled as self-contained
> examples for oe-core itself.
>
> There must be a simple way for people to setup the environment and run a build
> so they can test the oe-core itself.  But there should be nothing in the system
> that requires all of the components to exist, if there is, it should be clearly
> documented that it's not an example component.  (Even putting the word "example"
> in the name would be fine with me.  i.e. replacing "poky" with "example".)

I agree.  I'd like to see us provide example scripts for running qemu, 
setting up the build env and so forth.  And I expect that distros will 
still provide their own version as they see fit.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-03-03 14:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 17:30 oe-core cleanup Mark Hatle
2011-03-02 18:00 ` Richard Purdie
2011-03-02 18:27   ` Koen Kooi
2011-03-02 18:33     ` Mark Hatle
2011-03-02 19:18     ` Richard Purdie
2011-03-03  0:58       ` Tom Rini
2011-03-03  8:02         ` Koen Kooi
2011-03-03 12:10           ` Richard Purdie
2011-03-03 14:43             ` Mark Hatle
2011-03-03 14:49               ` Tom Rini [this message]
2011-03-03 12:46 ` Koen Kooi
2011-03-03 13:09   ` Joshua Lock
2011-03-03 13:57     ` Koen Kooi
2011-03-03 14:05       ` Joshua Lock
2011-03-03 14:14         ` Chris Larson
2011-03-03 14:21           ` Chris Larson
2011-03-03 14:31             ` Joshua Lock
2011-03-03 14:29           ` Joshua Lock
2011-03-03 14:15       ` Chris Larson

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=4D6FAA81.1020306@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-core@lists.openembedded.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.