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: Mon, 13 Jun 2011 22:30:20 +0100 [thread overview]
Message-ID: <1308000620.15712.288.camel@rex> (raw)
In-Reply-To: <49501374-7FBE-400E-A91B-BD7EBD7FB65C@dominion.thruhere.net>
On Mon, 2011-06-13 at 22:36 +0200, Koen Kooi wrote:
> Op 13 jun 2011, om 22:28 heeft Saul Wold het volgende geschreven:
>
> > On 06/13/2011 11:31 AM, Koen Kooi wrote:
> >> Hi,
> >>
> >> Khem was asking if I could reproduce the recent x86 breakage he was seeing[1] and I ran into another bug:
> >>
> >> koen@dominion:/OE/tentacle/sources/meta-intel$ git blame meta-n450/conf/machine/n450.conf | grep atom
> >> 158f88d7 (Saul Wold 2011-01-03 15:33:52 -0800 6) require conf/machine/atom-pc.conf
> >>
> > meta-yocto seems to be the place you need to look!
> >
> > I hope that the layering tools can help to detect and inform folks of this like of dependency.
>
> Isn't meta-yocto supposed to a the integration layer with no new
> parts? I can't use meta-yocto since it has conflicting beagleboard
> stuff in it, which means that meta-intel is now broken for me as well.
> That surely isn't the intended plan?!?!
The plan on public record is that atom-pc moves to meta-intel as soon as
the layer tooling comes online and meta-yocto becomes its own repo
(which at present its not but its certainly the intent).
Cheers,
Richard
next prev parent reply other threads:[~2011-06-13 21:34 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 [this message]
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
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=1308000620.15712.288.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 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.