linux/poky.git/bitbake/lib/bb/data.py, branch yocto-2.7

bitbake: data/siggen: Switch md5 -> sha256

2019-01-08T11:16:03+00:00

Similarly to the codeparser change, change to sha256 hashes due to worries over collisions. The main impact of this change is slightly slower parsing time as well as longer sstate file names. (Bitbake rev: 66f1b766997d53b4375fdd25719b1175f3828903) Signed-off-by: Richard Purdie

bitbake: bitbake: BBHandler: Check tab indentation for python code

2018-12-05T13:04:54+00:00

The previous check was in data.py which only can check code like "python funcname()" in the dependency chain, but there are 3 kinds of python functions: - python() - def py_funcname() - python funcname() Add the checking to BBHandler to check and warn for all of them. The warning looks like: WARNING: /path/to/recipes-core/busybox/busybox_1.29.2.bb: python should use 4 spaces indentation, but found tabs in busybox.inc, line 75 (Bitbake rev: 0cdc5b81fc1f5e5281a525a657e420ebc3bb9e90) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: data/siggen: Extract task hash generation code into a function

2018-10-18T09:59:27+00:00

By creating a standalone function, we can add better functional testing of this code. (Bitbake rev: 796a20d24dc18479de1975a37b9e52a5ac75c73f) Signed-off-by: Richard Purdie

bitbake: bitbake: data: Ensure task checksums account for remove data

2018-10-18T09:59:27+00:00

Currently remove operations are not being accounted for in the task checksums. This is a fairly serious oversight and needs to be fixed. To do so, we need internal data from getVarFlag combined with the expanded variable data so that only "active" remove operators are accounted for in the task checksum. We can get this from the new optional removes attribute in the returned parser object. The code can then use the data on active remove operators to account for the removals in task checksum but only when the removal is active. We have to be careful here not to reference any expanded data since this may for example contain build paths. This means we can only map back and reference the unsplit (and hence unexpanded) remove string which may expand to multiple removal values. [YOCTO #12913] (Bitbake rev: 57d2ee17ae83a139a37081eb082e6184fa883581) Signed-off-by: Richard Purdie

bitbake: data/data_smart: Allow getVarFlag to return the variable parser object

2018-10-18T09:59:27+00:00

(Bitbake rev: 136100dc932c9019737f927d826955425134010f) Signed-off-by: Richard Purdie

bitbake: data: Micro performance optimisation tweak

2017-07-08T12:29:54+00:00

The datastore can assume internal API, this just removes the function indirection overhead involved in this very common codepath (800,000 calls in parsing OE-Core). (Bitbake rev: 9a36531ed2b2881a65e5d39ee4b68d2bb392ed78) Signed-off-by: Richard Purdie

bitbake: lib/bb/{data, siggen}: Don't warn on SkipRecipe exceptions

2017-04-12T14:16:05+00:00

Recipes/variables that raise a SkipRecipe exception are intentionally skipped, and should not generate warnings. [YOCTO #11319] (Bitbake rev: edf6e6094a9f7ad4b2ba06eef8fd34756edbedce) Signed-off-by: Nathan Rossi Signed-off-by: Richard Purdie

bitbake: lib/bb/data: fix dependency handling for contains and multiple values

2017-04-05T22:19:17+00:00

The code that determines variable dependencies uses the codeparser to find references to "contains" type operations e.g. bb.utils.contains(). That function can take multiple items to check, and all specified items have to be present. However this code didn't handle that - it assumed that only one item would be specified and thus it was treating the multiple items as a single item with spaces in between. Split the value and check if all words are present in order to determine whether the check is "set" or "unset". (Bitbake rev: 272f1245acdd4fb85cb78612aa03627a9c246d8f) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: data/cooker: Sort output data shown by -e

2017-03-22T11:35:23+00:00

Displaying the environment data in a sorted manner makes it easier to compare data between different setups and means you can know where to find specific entries. (Bitbake rev: baa417e44b009149eb1dfb07d5a488740b6e68ef) Signed-off-by: Richard Purdie

bitbake: data.py: sort exported variables

2017-03-22T11:35:23+00:00

Various run.do_xxx files export dozens of variables. Presently they are in random order. Among other things, this makes it difficult to compare two files for relevant changes. This patch ensures they are enumerated/printed in a sorted (alphabetical) order. (Bitbake rev: 27b501d1400d1942b5ba9f35218ca7aacd9bfefe) Signed-off-by: Juro Bystricky Signed-off-by: Richard Purdie