linux/poky.git/bitbake/lib/bb/data.py, branch 1.2_M1

bitbake: Update users of getVar/setVar to use the data store functions directly

2011-11-27T10:35:30+00:00

Signed-off-by: Richard Purdie

data/siggen: Add vardepvalue mechanism to allow the variable dependency code to be forced to specific values

2011-11-24T22:11:45+00:00

We have a problem if we want to inject specific information into the variable dependency code. There are cases for example where we want a dependency on the value of X but it doesn't matter how X was constructed or what dependencies it might have had, we only care about the absolute value. With the current code, its near enough impossible to do this. This patch adds such a mechanism so the user can trigger this with code like: baselib[vardepvalue] = "${baselib}" It also refactors some of the code so we do variable lookups once instead of doing this in two different functions. [YOCTO #1583] (Bitbake rev: 6c879b44ccf42dc73fe4467076e114700d7ba81b) Signed-off-by: Richard Purdie

codeparser: silence non-literal warnings for vardeps

2011-11-10T11:44:29+00:00

If the vardeps flag is not None, we now silence the warnings about non-literal usage for that variable. (Bitbake rev: e724b9f417d1baf898f5afc6376c73c1a2ad8db9) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

codeparser: accept a name for better messages

2011-11-10T11:44:29+00:00

- If a name is passed to the parser, prepend the messages with "while parsing :". This gives a bit more context. - Tweak the warning messages slightly (they had to be altered anyway to inject the variable being parsed). Before: DEBUG: Warning: in call to 'bb.data.getVar': argument ''%s' % var' is \ not a literal After: DEBUG: while parsing emit_pkgdata, in call of bb.data.getVar, argument \ ''%s' % var' is not a string literal (Bitbake rev: 1060193ae4d54e667735dbff5d1d2be49a3f95c9) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

Ensure only the filtered environment variables are inherited from the OS

2011-08-15T08:49:37+00:00

The recent change which modified inheritFromOS to use the intial environment, rather than the current environment, introduced a bug such that variables which had been cleaned from the environment where still set in the data store. This patch changes things such that a list of approved environment variables is saved after the environment is cleaned and only the variables in this list are inherited in inheritFromOS. CC: James Limbouris CC: Chris Larson (Bitbake rev: cb6c07054e8baf94614713ec257c643b22266d75) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

data|cooker: use saved environment variables when calling inheritFromOS

2011-07-26T12:46:27+00:00

Now that we have a pristine copy of the variables available at launch time we can use them when looking to inherit the OS's environment. (Bitbake rev: 21c21fcc5871e81d8d497b6baed605cdd74c4571) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

make exception handling syntax consistent

2011-06-15T10:13:13+00:00

Update exception handling syntax to use the modern style: except ExcType as localvar (Bitbake rev: dbf5f42b06bef81749b13aa99945cc1292a6676d) Signed-off-by: Scott Garman Signed-off-by: Richard Purdie

bitbake/data/runqueue: Sync up with upstream to clean up environment variable handling

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

Signed-off-by: Richard Purdie

bitbake/siggen.py: Fix whitelisted variable handling

2011-01-12T15:58:48+00:00

Even when a variable was whitelisted, any dependencies of that variable could still creep into the task hash due to the way the whitelisting code worked. This patch changes thing to ensure that when whitelisted, that whitelisting applies to the variable and any dependencies it has. Signed-off-by: Richard Purdie

bitbake: Sync environment handling function names and comments with upstream alterations

2011-01-10T13:24:03+00:00

Signed-off-by: Richard Purdie