Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: 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:24:23 +0100	[thread overview]
Message-ID: <201106140124.23185.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <BANLkTinh1G+8fKDAiGnCyzWXoVV=MoAEfg@mail.gmail.com>

On Tuesday 14 June 2011 01:09:27 Otavio Salvador wrote:
> I know the delta is getting smaller and smaller. This is good. A good
> way to make it move faster is using OE-Core as basis. This will
> "force" the backporting of missing Poky's change to OE-Core to happen
> faster.

We *are* using oe-core as a basis. The thing limiting us right now is the lack 
of appropriate layer tooling, something which is being worked on right now and 
should arrive very soon - in fact the combo layer tool you responded to 
earlier is the most important piece that we need to fix this integration issue.

> Currently there're many people that base the stuff (that is target to
> OE-Core) on Poky and sometimes it cases issues (as the bitbake ones I
> used as example).

Since bitbake upstream and the one in poky are now very close (differences 
almost negligible) and we now send all of our changes via upstream first, I 
would not expect any more bitbake divergence in future.

I'm not saying we can't do better or we shouldn't test with oe-core alone - we 
definitely should do the latter more often. I can only reiterate what Richard 
has said - bear with us, we're working on it :)

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-06-14  0:27 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
2011-06-14  0:09                   ` Otavio Salvador
2011-06-14  0:24                     ` Paul Eggleton [this message]
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=201106140124.23185.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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