All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
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 15:20:15 -0500	[thread overview]
Message-ID: <1308082816.10825.38.camel@elmorro> (raw)
In-Reply-To: <BA4956B5-23B8-4590-8B23-A9837D6A11EA@dominion.thruhere.net>

On Tue, 2011-06-14 at 00:40 -0700, Koen Kooi wrote:
> Op 13 jun 2011, om 23:30 heeft Richard Purdie het volgende geschreven:
> 
> > 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).
> 
> So can someone at least put that in the meta-intel or meta-n450 README? Most layers now have a README with the dependency info (e.g. http://git.shr-project.org/git/?p=meta-smartphone.git;a=blob;f=meta-palm/README;h=200a3c83ff11ad790fe4e03e93a26520ec0c6714;hb=HEAD ) It would be nice if the ones on yocto-project.org had somethign similar :)
> _

Would something like this do the trick for now (if so, I can do similar
for the other meta-intel bsps)?

From ae612a895b320471f65e289328fd351d4094a7c2 Mon Sep 17 00:00:00 2001
Message-Id:
<ae612a895b320471f65e289328fd351d4094a7c2.1308077431.git.tom.zanussi@intel.com>
From: Tom Zanussi <tom.zanussi@intel.com>
Date: Tue, 14 Jun 2011 13:49:24 -0500
Subject: [PATCH] meta-n450: add dependency info

Add information on the dependencies needed to use the meta-n450 layer.

Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
---
 meta-n450/ReleaseNotes |   30 ++++++++++++++++++++++++++++++
 1 files changed, 30 insertions(+), 0 deletions(-)

diff --git a/meta-n450/ReleaseNotes b/meta-n450/ReleaseNotes
index 23ac815..4257d94 100644
--- a/meta-n450/ReleaseNotes
+++ b/meta-n450/ReleaseNotes
@@ -1,8 +1,38 @@
 Poky Laverne Release 4.0
 
+- Dependencies
 - Features and Updates
 - Known Issues
 
+DEPENDENCIES
+============
+
+This layer depends on:
+
+  URI: git://git.openembedded.org/bitbake
+  branch: master
+
+  URI: git://git.openembedded.org/openembedded-core
+  layers: meta
+  branch: master
+
+  URI: git://git.yoctoproject.org/poky
+  layers: meta-yocto
+  branch: master
+
+NOTE: n450 currently depends on meta-yocto due to atom-pc
+dependencies.  The plan is to move atom-pc to meta-intel as soon as
+the layer tooling comes online and meta-yocto becomes its own repo.
+At that point, meta-yocto will no longer be required.
+
+Note also that the layering with respect to the poky repo is in
+transition; it currently contains both meta from openembedded-core and
+bitbake along with some other files and directories which will
+eventually be contained in standalone repos once the ongoing layering
+work has been completed.  As such, the master branch of the poky repo
+can at the present time be used to satisfy all meta-intel
+dependencies.
+
 
 FEATURES AND UPDATES
 ====================
-- 
1.7.0.4



> ______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core





  reply	other threads:[~2011-06-14 20:23 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
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 [this message]
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=1308082816.10825.38.camel@elmorro \
    --to=tom.zanussi@intel.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.