[oe] [PATCH 1/2] bitbake.conf, collections.inc: Add COLLECTIONS mechanism w/ a sane default.

[Chris Larson]

On Fri, Apr 3, 2009 at 1:54 AM, Holger Schurig
<hs4233 at mail.mn-solutions.de> wrote:
> On Thursday 02 April 2009 02:27:17 Chris Larson wrote:
>> COLLECTIONS = "${@' '.join(d.getVar('BBPATH', 1).split(':'))}"
>
> Why do we need a new variable here?  Can't we just use the
> equivalent BBPATH.split()  ??  Or is there a use-case where it
> makes sense to have BBPATH != COLLECTIONS ?

Yes, there are a number of possible cases.  For one, consider someone
with a ~/oe, under which they have multiple work areas, each with
their own trees.. say, poky, a local company specific metadata repo,
and upstream oe.  Also consider that ~/oe is in BBPATH, so that
~/oe/conf/site.conf can be used for those trees.  This is exactly the
setup I have on a few of my workstations.  If I were to let it use the
BBPATH based setup always, I'd always have *all* the recipes from
*all* those trees being parsed.  Not optimal.  In addition, the
followup patch to facilitate archive based collections wouldn't be
feasable in that case.
-- 
Chris Larson
clarson at kergoth dot com
clarson at mvista dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Software Engineer
MontaVista Software, Inc.