linux/poky.git/bitbake/lib/bb/taskdata.py, branch 1.2_M4

taskdata: fix string formatting of an error message

2011-09-20T21:22:21+00:00

(Bitbake rev: 224db31c46f5e91ced0e509c5fc564baaffa7b27) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

Fixup remaining bb.msg.domain users

2011-08-15T16:31:52+00:00

(Bitbake rev: d5abdacaf9ac604ef8d8c1bafb9b30617827cb4f) Signed-off-by: Richard Purdie

bitbake/taskdata: fix incorrect usage of rdependees instead of dependees

2011-07-27T15:54:04+00:00

This looked like a copy-paste error - the code around is dealing with depends and not rdepends. (Bitbake rev: bb688635c2050da3cbbaa5aa5b00e882887695de) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: show more information for NoProvider errors

2011-07-27T15:54:04+00:00

"Nothing PROVIDES" errors often come up when a recipe has been skipped for some reason, and therefore it is useful to print out that reason information when showing the error so that the user understands why the error has occurred. Given that we already feed the reason information into the skiplist for various situations (COMMERCIAL_LICENSE, COMPATIBLE_MACHINE etc.) this should now output a useful error message for skipped recipes. Fixes [YOCTO #846], [YOCTO #1127] (Bitbake rev: 6765218430e31c165888f26fbc75023c89a6eab2) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

cooker: use re match, not search in re_match_strings

2011-01-04T14:46:47+00:00

We want to match the requested pattern at the beginning of the string, otherwise things behave in an unintuitive manner wrt ASSUME_PROVIDED (e.g. ASSUME_PROVIDED += "gtk+" will also assume foo-gtk+ is provided), and the user can always use '.*gtk+' to get the old behavior. (Bitbake rev: 5670134ab2eb573d39df3c3231677cdb1a1dfc72) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

taskdata: use 'any' in re_match_strings

2011-01-04T14:46:47+00:00

(Bitbake rev: e48e9a2150ee76aaf151f6d5bc9e86e6ae4de514) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Prefer xrange over range for small performance gain.

2011-01-04T14:46:42+00:00

range() allocates an actual list when called. xrange() is just an iterator and creates the next range item on demand. This provides a slight performance increase. In python 3, range will do what xrange does currently, but the upgrade will be handled by the 2to3 tool. (Bitbake rev: 73b40f06444cb877a5960b2aa66abf7dacbd88f0) Signed-off-by: Bob Foerster Signed-off-by: Richard Purdie

Pre-explode rundeps/runrecs in CacheData

2011-01-04T14:46:40+00:00

(Bitbake rev: 0c8e0f3191252ccedb83c431c48e5c7d905e2717) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Fix providerlog NameError

2011-01-04T14:46:34+00:00

(Bitbake rev: 992e460f24d4da707c76d6e6d74d3684c9646279) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Switch bitbake internals to use logging directly rather than bb.msg

2011-01-04T14:46:33+00:00

We use a custom Logger subclass for our loggers This logger provides: - 'debug' method which accepts a debug level - 'plain' method which bypasses log formatting - 'verbose' method which is more detail than info, but less than debug (Bitbake rev: 3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie