linux/poky.git/bitbake/lib/bb/ui/goggle.py, branch mickledore

bitbake: goggle/image-writer: Drop since bitrotting and no longer used

2016-06-02T07:24:03+00:00

The upgrade to python3 is the final nail in the coffin for image-writer and the goggle UI. Neither seem used or recieve patches and are based on old versions of GTK+ so drop them, and the remaining crumbs support pieces. (Bitbake rev: ee7df1ca00c76f755057c157c093294efb9078d8) Signed-off-by: Richard Purdie

bitbake: bitbake: Convert to python 3

2016-06-02T07:24:02+00:00

Various misc changes to convert bitbake to python3 which don't warrant separation into separate commits. (Bitbake rev: d0f904d407f57998419bd9c305ce53e5eaa36b24) Signed-off-by: Richard Purdie

bitbake: cooker: Rename confusing 'stop' state to 'forceshutdown'

2013-09-14T07:20:38+00:00

The shutdown state causes the server to finish what its doing, stop was them meant to completely stop it. It doesn't mean the server is stopped though. Renaming the current stop event for forceshutdown gives more meaning to what it actually does. The stopped namespace then becomes available to indicate a completely stopped server. (Bitbake rev: 12e9d33bfae5294e3870dfd1202f63383ad05e92) Signed-off-by: Richard Purdie

bitbake: cooker: Move commandline parsing back into the UI/cookerdata

2013-05-22T11:10:13+00:00

Building up a set of actions for the server is tricky since we depend upon the commandline but fall back to values from the datastore. We should be able to build a datastore without a commandline and vice versa. Ultimately the UI should send the commands to the server. This patch amounts to code rearranging, moving the heavy lifting to the UI, though a helper in the configuration option. This will need further cleanup/tweaking but this should be the only update needed to the UIs. The code now queries the server for any missing data should it need to. This code allows various knowledge of configuration variables to move to the UI side only, partcularly pkgs_to_build but also all the command specifiers. It should also be possible to move cmd eventually, I'm just unsure if any callers call the commands expecting this to default to something sane right now. (Bitbake rev: 2dbbb1d51dafd4451fef8fe16f095bcd4b8f1177) Signed-off-by: Richard Purdie

bitbake: goggle: fix invalid error check

2013-05-03T15:24:13+00:00

runCommand was returning 'error' but checking for 'err' resulting in an exception. (Bitbake rev: 263aa44ed47e0cb03e1a97e7ed4a50bd9f828c78) Signed-off-by: Martin Donnelly Signed-off-by: Richard Purdie

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 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

goggle: exit quietly on ^C

2011-03-31T11:20:54+00:00

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

bitbake/goggle: don't drop events

2011-01-12T11:43:50+00:00

We had a logic inversion that meant we where dropping quite a significant number of events on the floor.... Fixed! Signed-off-by: Joshua Lock

bitbake/goggle: closing the progress dialog kills the UI

2011-01-12T11:43:50+00:00

It's unlikely that someone wants to close the progress dialog yet leave the UI (and BitBake process) running, so hook up the progress dialogs delete-event to exit gtk. Signed-off-by: Joshua Lock