Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Where is atom-pc.conf hiding?
Date: Tue, 14 Jun 2011 01:02:00 +0100	[thread overview]
Message-ID: <1308009720.15712.319.camel@rex> (raw)
In-Reply-To: <BANLkTi=035xAQJS5kwhUGvDiGsanfD_FKQ@mail.gmail.com>

On Mon, 2011-06-13 at 23:17 +0000, Otavio Salvador wrote:
> On Mon, Jun 13, 2011 at 23:04, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> ...
> > So on the one hand I do understand your concern. I'm personally and
> > Yocto are doing the best we can. On the other I'd suggest if testing
> > certain combinations is this important to you (or Mentor?), stepping up
> > and helping with the testing would be *much* appreciated and it isn't
> > the sole responsibility of myself or Saul.
> ...
> 
> It would be easier and better if people at Yocto could start basing
> their work on oe-core so stuff get tested there instead of Poky. Poky
> would then be an integration point not a base.

Have you looked at the delta recently? Yocto uses OE-Core with the
single addition of the meta-yocto layer which is tiny. Just like
angstrom use the meta-angstrom layer and the meta-oe layer. 

> More then once I got broken trees for stuff that were pushed to
> oe-core and were not working due missing fixes or features that were
> pushed to Poky's bitbake but not to the upstream one.

Again, please look at the delta between upstream bitbake and the one in
poky. All bitbake patches are now landing upstream first. There were
issues, we came up with a plan to address them and we're doing what we
said we would do...

> Doing this would help to improve it a lot. For example meta-intel
> would be already fixed since people would be using it against oe-core
> and would have already noticed the missing machine  definition and
> like.

We *know* the machine definition isn't there, its deliberate. We came up
with a plan to create OE-Core and to get Poky and OE both migrated to
using it. This process is not 100% complete yet although it gets closer
every day.

Cheers,

Richard





  reply	other threads:[~2011-06-14  0:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 18:31 Where is atom-pc.conf hiding? Koen Kooi
2011-06-13 20:28 ` Saul Wold
2011-06-13 20:36   ` Koen Kooi
2011-06-13 21:30     ` Richard Purdie
2011-06-13 22:10       ` Tom Rini
2011-06-13 22:19         ` Otavio Salvador
2011-06-13 22:35         ` Richard Purdie
2011-06-13 22:44           ` Tom Rini
2011-06-13 23:04             ` Richard Purdie
2011-06-13 23:17               ` Otavio Salvador
2011-06-14  0:02                 ` Richard Purdie [this message]
2011-06-14  0:09                   ` Otavio Salvador
2011-06-14  0:24                     ` Paul Eggleton
2011-06-14  7:44         ` Phil Blundell
2011-06-14 12:05           ` Richard Purdie
2011-06-14  7:40       ` Koen Kooi
2011-06-14 20:20         ` Tom Zanussi
2011-06-14 21:08           ` Koen Kooi
2011-06-14 21:33             ` Tom Zanussi
2011-06-13 20:29 ` Joshua Lock

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=1308009720.15712.319.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox