linux/poky.git/bitbake/lib/bb/shell.py, branch sumo

lib/bb/shell.py: drop

2018-03-28T11:59:37+00:00

This was removed in the bitbake repository back in 2010 (bitbake revision 24857e2ceb405916b0b0b3e75c6c2375a909b9ba) - it's not clear to me what happened, but for some reason the file remained in the poky repository. However it does not appear that it has been used since then and the reasons for removing even more valid now than they were then - the code has moved on even further, we have memory resident bitbake server, and if we were to re-implement this we would do it in a different way. Drop the file and bring us back in sync with the bitbake repo. Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

Introduce new param caches_array into Cache impl.

2011-06-07T21:39:52+00:00

When using hob ui interface, we need extra cache fields. We will save ui required extra cache fields into a separate cache file. This patch introduce this caches_array parameter. It will be used in the extra cache implementation (following patch). Caches_array at least contains CoreRecipeInfo. If users need extra cache fields support, such as 'hob', caches_array will contain more relevant elements such as HobRecipeInfo. (Bitbake rev: d50389ae692377c957afec7c846fc2ce2c070a09) Signed-off-by: Liping Ke

cooker: stop loading the cache for -b

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

Previously, the cache was actually being loaded from disk twice whenever using -b or -e -b. This also moves the bb_cache instance into the CookerParser, as it's not needed by the cooker itself at all. (Bitbake rev: dd0ec2f7b18e2a9ab06c499b775670516bd06ac8) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Simplify build exception handling

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

- Drop EventException - Use FuncFailed as the primary function failure exception, using TaskFailed for the event (leaving it up to the process running exec_{func,task} to display the more detailed information available in the exception). - Switch InvalidTask to an exception rather than an event, as that's a critical issue. - Reduce the number of messages shown to the user when a task fails -- they don't need to be told it fails 12 times. Work remains in this area though. (Bitbake rev: 06b742aae2b8013cbb269cc30554cff89e3a5667) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Apply some 2to3 refactorings

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

Signed-off-by: Richard Purdie

Fix syntax error in shell.py

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

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

Apply the 2to3 print function transform

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

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

Import fixups

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

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

Formatting cleanups

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

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

Avoid unnecessary calls to keys() when iterating over dictionaries.

2010-03-22T15:01:59+00:00

dict objects provide an __iter__ method for the iteration which gives you the keys, so calling keys directly is unnecessary, and isn't really a best practice. The only time you really need to call the keys is if there's a danger of the dict changing out from underneith you, either due to external forces or due to modification of the iterable in the loop. Iterations over os.environ are apparently subject to such changes, so they must continue to use keys(). As an aside, also switches a couple spots to using sorted() rather than creating a temporary list with keys() and sorting that. (Bitbake rev: 5b6ccb16c6e71e23dac6920cd2df994d67c2587b) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie