linux/poky.git/bitbake/lib/bb/utils.py, branch fido-13.0.0

bitbake: cooker: rework LAYERDEPENDS versioning so that it is actually useful

2015-02-16T09:10:42+00:00

We've had versioned dependency support in LAYERDEPENDS for quite a long time, but I can say with pretty good certainty that almost nobody has used it up to now because it was too strict - the specified version had to exactly match the version in your configuration or you would get an error; there was no "greater than or equal" option, which is usually what you will want given that LAYERVERSION does get bumped from time to time. However, users mismatching layer branches and then having their builds fail later on with some incomprehensible error is still a pretty common problem. We can't simply use the git branch because not everyone is always on a branch and the branch names don't always match up (and that's not an issue). To provide a practical means to address branch mismatching, I have reworked LAYERDEPENDS version specifications to use the more familiar "dependency (>= version)" syntax as used with package dependencies, support non-integer versions, and clarified the error message a little. If we then take care to bump the version on every breaking change, it is at least possible to have layers depend on these changes when they update to match; we can now even support a major.minor scheme to allow retrospectively adding a version limiter to old branches when a new branch is created and yet still allow the old branch minor version to be bumped if needed. Fixes [YOCTO #5991]. (Bitbake rev: 408be9cdf2b1e32e64ea488d8051a546fb54c144) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: utils: ensure explode_dep_versions2 raises an exception on invalid/missing operator

2015-02-16T09:10:42+00:00

We really want an error rather than the version to just be silently skipped when the operator is missing (e.g. "somepackage (1.0)" was specified instead of "somepackage (>= 1.0)".) (Bitbake rev: b6dc946f477adc40d68da16e2f2580cb3b4a10db) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: utils: make edit_metadata_file() handle VARIABLE +=

2014-12-30T09:21:42+00:00

This is a little crude as the usage basically ignores that you're doing an append operation, but for a lot of cases it will be sufficient. (Bitbake rev: 24a28205ab680b6cc645d97b76c9855920608229) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: bitbake-layers: fix error handling in add-layer / remove-layer

2014-12-30T09:21:42+00:00

* Fix add-layer error message when a layer is already in BBLAYERS * Ensure we show an error message if we can't find BBLAYERS at all (Bitbake rev: 1c743fd2103730e27699dd55efc6914d3b0c3702) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: utils: add basic metadata manipulation functions

2014-12-23T10:18:20+00:00

* Add a generic edit_metadata_file() function to modify variable assignments in any metadata file (conf, bb, bbappend) using a callback for flexibility * Add a specific edit_bblayers_conf() function to modify conf/bblayers.conf and add and/or remove layers from the BBLAYERS value within it. (Bitbake rev: aa03a28b442549dd8ffe92ae4d6390f62202a76a) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: utils: add exec_flat_python_func()

2014-12-09T22:15:48+00:00

Add a function that allows executing a flat python function (defined with def funcname(args): ...). (Bitbake rev: 20e6939ebcb62e08a9a7ad586a915dfe368136a0) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: utils.py: don't use len() for truth value testing.

2014-10-28T14:58:34+00:00

(Bitbake rev: 4bdfeab7845bdcd62a4928200dd13701414a464e) Signed-off-by: Oscar Utbult Signed-off-by: Richard Purdie

bitbake: utils: Improve profile log processing

2014-08-28T14:12:45+00:00

This stream redirection of stdout is horrible. pstats takes a stream argument so lets use that instead. (Bitbake rev: 93d155f4766e27e7b004d13569aa03961fe89e3b) Signed-off-by: Richard Purdie

bitbake: lib/bb/*.py: Typo fixes/grammar/comment fixes, nothing functional.

2014-08-25T07:57:45+00:00

(Bitbake rev: 587b144ee409d444494d8d7f2d1c53ede8f7c953) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie

bitbake: utils: Add workaround for multiprocessing bug

2014-08-23T08:31:42+00:00

Our usage of multitprocessing is problematic. In particular, there is a bug in python 2.7 multiprocessing where signals are not handled until command completion instead of immediately. This adds a workaround into our wrapper function to deal with the issue. (Bitbake rev: a16185e602b39b71475aa7e9ee80ad2b1f28d0f7) Signed-off-by: Richard Purdie