All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Puhlman <jpuhlman@gmail.com>
To: Yocto Mailer <yocto@yoctoproject.org>
Cc: dvhart@linux.intel.com
Subject: In consistancy in the defition of BBFILE_COLLECTIONS in layer.conf
Date: Wed, 25 May 2011 18:17:44 -0700	[thread overview]
Message-ID: <4DDDAA38.8070404@gmail.com> (raw)

Opps sent from wrong account.

I was working with some layerinfo code, and I noticed that the values of
BBFILE_COLLECTIONS in layer.conf in the meta-intel repo are kind of all over the map:

 for each in */conf/layer.conf; do cat $each; done | grep BBFILE_COLLECTIONS
BBFILE_COLLECTIONS_crownbay += "crownbay"
BBFILE_COLLECTIONS_crownbay-noemgd += "crownbay-noemgd"
BBFILE_COLLECTIONS_fishriver += "fishriver"
BBFILE_COLLECTIONS_jasperforest += "jasperforest"
BBFILE_COLLECTIONS_sugarbay += "sugarbay"

For the above layers when I just list out oe-core and one of the above,
the results from BBFILE_COLLECTIONS ends up
just being what ever was set above.

BBFILE_COLLECTIONS += "n450"
BBFILE_COLLECTIONS += "emenlow"

When using these layers, the final BBFILE_COLLECTIONS is the list of all
the layers as expected.

Was just curious if there was a intentional reason why the
difference(i.e. is there some code that I am missing that fixes this up)?
-- Jeremy Puhlman Montavista Sofware, LLC.



             reply	other threads:[~2011-05-26  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  1:17 Jeremy Puhlman [this message]
2011-05-26  3:37 ` In consistancy in the defition of BBFILE_COLLECTIONS in layer.conf Tom Zanussi
2011-05-26  3:49   ` Jeremy Puhlman
2011-05-26  7:39   ` Martin Jansa
2011-05-26  9:49     ` Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2011-05-26  0:54 Jeremy Puhlman

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=4DDDAA38.8070404@gmail.com \
    --to=jpuhlman@gmail.com \
    --cc=dvhart@linux.intel.com \
    --cc=yocto@yoctoproject.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.