linux/poky.git/bitbake/lib/bb/cache.py, branch green-3.3.1Mirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=green-3.3.12010-03-25T17:28:34+00:00cache.py: Bump the cache version after the BBVERSIONS update2010-03-25T17:28:34+00:00Richard Purdierpurdie@linux.intel.com2010-03-25T17:28:34+00:00urn:sha1:fb245be03d8e3327165033045245f5f853c0b0d4
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Implement BBVERSIONS2010-03-25T17:25:45+00:00Chris Larsonchris_larson@mentor.com2010-03-20T00:22:19+00:00urn:sha1:c24424327409544807a781bba4e6f9a8e178dcce
This implements a feature similar to BBCLASSEXTEND, but for generating
multiple versions of a given recipe. For example: BBVERSIONS = "1.0 2.0 git".
In addition to the above, one can utilize [a-b] style patterns, and can have a
:<basever> postfix, which allows you to essentially name the range of
versions. Both the current version and the basever end up in OVERRIDES, and
the basever gets placed into the BPV variable. The default BPV, if none is
specified, is the original PV of the recipe, before bbversions processing.
In this way, you can do things like:
BBVERSIONS = "1.0.[0-6]:1.0.0+
1.0.[7-9]:1.0.7+"
SRC_URI_append_1.0.7+ = "file://some_extra_patch.patch;patch=1"
Or you can create a recipe per range, and name the recipe file as such: nano_1.0.7+.bb.
(Bitbake rev: 4ee9a56e16f1eb3c1649eaa3127b09ab0e93d1ec)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: [cache] copy instead of deepcopy in sync2010-02-15T17:07:58+00:00Holger Freytherich@tamarin.(none)2009-05-17T03:59:06+00:00urn:sha1:defa54dea07a614c6ca0fe85512ab3d41d5d7edc
We only intend to modify the dict, no need to copy all
elements.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: Switch to bitbake-dev version (bitbake master upstream)2010-01-20T18:46:02+00:00Richard Purdierpurdie@linux.intel.com2010-01-20T18:46:02+00:00urn:sha1:22c29d8651668195f72e2f6a8e059d625eb511c3
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: Sync various functions with those from bitbake-dev and bitbake upstream2009-11-13T12:15:21+00:00Richard Purdierpurdie@linux.intel.com2009-11-03T23:20:15+00:00urn:sha1:483f85802a97cb9ad4d958c29458db91acc7809f
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake/cache.py: Add warnings for leakage of SRCREVINACTION magic value2009-09-24T17:57:09+00:00Richard Purdierichard@ted.(none)2009-09-22T18:53:34+00:00urn:sha1:bec200b38d96f2d766045daa36a6235151ea4e19
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake cache: Add code to catch a nasty cache corruption issue to aid in tracking it down2009-09-03T21:57:26+00:00Richard Purdierpurdie@linux.intel.com2009-09-03T21:57:26+00:00urn:sha1:bc0b233c02d6ffa89633551fd1b77a7a55df6a03
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: Update to work without warnings with python 2.62009-05-12T15:53:22+00:00Richard Purdierpurdie@linux.intel.com2009-05-12T15:53:22+00:00urn:sha1:81ff3a90f8f4ee0a00c439be9a1438de6c2ec168
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: Add in code to support the BBCLASSEXTEND variable. Virtual native/sdk recipes then become possible2009-01-03T16:25:20+00:00Richard Purdierpurdie@linux.intel.com2009-01-01T14:43:54+00:00urn:sha1:ade351e2f4c3693d4c2ecf3891899c2dcd082491bitbake/cache.py: Simplify logic2009-01-03T00:10:10+00:00Richard Purdierpurdie@linux.intel.com2009-01-02T23:57:03+00:00urn:sha1:28fd9dadbdf842d5db32e893be85068f9b2b114a