linux/poky.git/bitbake/lib/bb/event.py, branch 1.2_M2.rc1

cooker: remove command import in cooker.py

2012-01-06T15:55:57+00:00

There is no direct use of command in cooker.py, and it is using bb.command instead. Remove command in the import list. This fixes a problem of embedded import between command.py and cooker.py. (Bitbake rev: c353316b2efcc7a893d6b4aa9a9647d51a6f69e3) Signed-off-by: Dongxiao Xu Signed-off-by: Richard Purdie

bitbake/event: Allow event handlers to quietly raise SkipPackage events

2011-09-02T17:15:27+00:00

(Bitbake rev: 2a7c92bdadf9a86d9ea2ea0c128108e38e0e97e5) 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

event: fix the event display order when exiting early

2011-07-21T21:46:37+00:00

It was displaying the log messages in LIFO order, which isn't what we expect to see. Thankfully this only occurred during an early abort (e.g. config file parsing error), but those are the cases where it's very important to see accurate messages, to diagnose. (Bitbake rev: b838e0f3a1b481c295f66f5c9f561fa4d51de673) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

cooker|command|event: add new command findFilesMatchingInDir

2011-07-01T16:17:35+00:00

This command can be used to search each BBPATH for files in the passed directory which have a filename matching the supplied pattern. This is implemented for use from the GUI (to determine the available PACKAGE_CLASSES) but has been written so as to be generically useful and reusable. (Bitbake rev: 2a599812a57cb0b964880a6a2b7548423497ea92) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

command|cooker|event: add findConfigFilePath command

2011-07-01T16:17:35+00:00

This takes the name of a .conf file and returns the full path to it (Bitbake rev: 22c8600b885faf841795b872d82f68dfb644a26e) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

bitbake/event/ast: Add RecipePreFinalise event

2011-06-09T21:43:46+00:00

One of the implications is we need to register the event handlers before executing the anonymous python functions. I can't find any issue with making that change in any existing metadata use cases. (Bitbake rev: a981df3cc9bf410d24f39919959952bdc6c76d03) Signed-off-by: Richard Purdie

Shift exception formatting into the UI

2011-06-08T19:38:25+00:00

Now we use bb.exceptions to pass pickleable traceback entries to the UI, and the UI is free to do whatever it wants to do with this information. By default, the log formatter for the UIs formats it with bb.exceptions. This also means that all exceptions should now show 3 lines of context and limit to 5 entries. (Bitbake rev: ee48d628ee038bd72e1cd94aa75f5ccbacbcee4c) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

bitbake none/xmlrpc servers: Only send pickled events to the xmlrpc server

2011-06-08T10:38:15+00:00

Only the xmlrpc server needs pickled events. Use the function names to signify this requirement. Signed-off-by: Richard Purdie

event: don't catch systemexit from handler execution

2011-06-02T22:58:05+00:00

This means that anyone firing an event can get a systemexit and result in their process exiting, which isn't ideal, but behaves the way it used to (in particular, ensures that a sanity check failure will halt the build). This should be revisited in the future. (Bitbake rev: d6a0ffdd583be3df734171d7e91d334f798a79ce) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie