linux/poky.git/bitbake/lib/bb/ui/ncurses.py, branch 1.4_M5

bitbake: command: add error to return of runCommand

2012-11-01T11:46:22+00:00

Currently, command.py can return an error message from runCommand, due to being unable to run the command, yet few of our UIs (just hob) can handle it today. This can result in seeing a TypeError with traceback in certain rare circumstances. To resolve this, we need a clean way to get errors back from runCommand, without having to isinstance() the return value. This implements such a thing by making runCommand also return an error (or None if no error occurred). As runCommand now has a method of returning errors, we can also alter the getCmdLineAction bits such that the returned value is just the action, not an additional message. If a sync command wants to return an error, it raises CommandError(message), and the message will be passed to the caller appropriately. Example Usage: result, error = server.runCommand(...) if error: log.error('Unable to run command: %s' % error) return 1 (Bitbake rev: 717831b8315cb3904d9b590e633000bc897e8fb6) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

bitbake: event.py, knotty.py, ncurses.py, runningbuild.py: Add support for LogExecTTY event

2012-09-24T14:35:32+00:00

The LogExecTTY even is intended to provide the ability to spawn a task on a the controlling tty, if a tty is availble. When a controlling tty is not availble the previous behavior is preserved where a warning is issued about the action an end user must execute. All the available UI's were tested against the new event type. This feature is primarily intended for hooking up a screen client session automatically on the controlling tty to allow for a more streamlined end user experience when using a pure command line driven environment. The changes that send the LogExecTTY event are in the oe-core side. (Bitbake rev: cffe80d82a46aaf52ff4a7b6409435754043553f) Signed-off-by: Jason Wessel Signed-off-by: Richard Purdie

bitbake: ui: Improve error message if bitbake cannot import python curses module

2012-08-22T12:59:57+00:00

On some SuSE systems, the curses python module is not installed by default. Instead of a python failure, we want a nicer error message. (On SuSE systems the package is typically python-curses.) (Bitbake rev: 65a5845ac942d0aa6838c295e41b656f9d2a98bb) Signed-off-by: Konrad Scherer Signed-off-by: Jeff Polk Reword commit message, rebase to latest bitbake. Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

replace os.system with subprocess.call

2012-05-23T10:35:11+00:00

Replace os.system with subprocess.call since the older function would fail (more or less) silently if the executed program cannot be found More info: http://docs.python.org/library/subprocess.html#subprocess-replacements [YOCTO #2075] (Bitbake rev: f5b3bf115dc1ffbfb241a49cec0fc3654cb71021) Signed-off-by: Robert Yang 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 cooker/ui: handle cmd line parsing result by individual UI.

2011-07-08T16:38:42+00:00

Changed the return result of "getCmdLineAction" to a dictionary {'action', 'msg'} to allow the individual UI decide how to handle the cmd line parsing result. (Bitbake rev: 521909d1350a415d19516aa1710041e30950c7cc) Signed-off-by: Lianhao Lu Signed-off-by: Richard Purdie

Resurrect alternative UIs

2011-01-05T11:13:48+00:00

The various alternative UIs have been updated to once again be functional with the latest bitbake internals. Each of the UIs still have much room for functional improvement. In particular, they have been updated to: - interact with the new process based server - handle the current set of events and notifications fired from the server and its associated subsystems (Bitbake rev: b947e7aa405966262c0614cae02e7978ec637095) Signed-off-by: Bob Foerster Signed-off-by: Richard Purdie

Rename command events, adjust compareRevisions

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

- Moved the logic for comparing revisions from cooker into command - Removed 'Cooker' from the event names - Renamed the 'ExitCode' event into CommandExit, and changed CommandFailed to be a subclass of CommandExit (Bitbake rev: c51ed5d7a9971fad6019dac6c35a71b8a54ab16a) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Rename the ui 'init' method to 'main'

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

As these may run the UI in a blocking fashion and then return the exit code, 'init' was an inappropriate name, and 'main' is more appropriate. (Bitbake rev: 4d081a0ed759bd526ab01849d650bd9e8d80ddd1) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

3.0 prep

2010-07-02T14:41:37+00:00

Signed-off-by: Richard Purdie