<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/lib/bb/data.py, branch 1.1_M1</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=1.1_M1</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=1.1_M1'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2011-01-12T15:58:48+00:00</updated>
<entry>
<title>bitbake/siggen.py: Fix whitelisted variable handling</title>
<updated>2011-01-12T15:58:48+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-01-12T15:58:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=25b3d39612c0bea1d136e346d938abde56aa699f'/>
<id>urn:sha1:25b3d39612c0bea1d136e346d938abde56aa699f</id>
<content type='text'>
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 &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: Sync environment handling function names and comments with upstream alterations</title>
<updated>2011-01-10T13:24:03+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2011-01-10T12:03:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c1864191732a4d221b02f0bce58129fb29e714d2'/>
<id>urn:sha1:c1864191732a4d221b02f0bce58129fb29e714d2</id>
<content type='text'>
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake/data.py: corrected the output for shell syntax.</title>
<updated>2011-01-07T11:14:22+00:00</updated>
<author>
<name>Lianhao Lu</name>
<email>lianhao.lu@intel.com</email>
</author>
<published>2011-01-07T06:17:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6f454c10bcdd5245ea9297f5334fc56ac06dbdb9'/>
<id>urn:sha1:6f454c10bcdd5245ea9297f5334fc56ac06dbdb9</id>
<content type='text'>
[BUGID# 645], modify the emit_var()
1. Added "#" to the beginning of each line if the comment contains
multiple lines.

2. Added "\" to the end of each line if the shell variable value
contains multiple lines.

Signed-off-by: Lianhao Lu &lt;lianhao.lu@intel.com&gt;
</content>
</entry>
<entry>
<title>data: fewer newlines for (un)export</title>
<updated>2011-01-04T15:00:11+00:00</updated>
<author>
<name>Bernhard Reutner-Fischer</name>
<email>rep.dot.nop@gmail.com</email>
</author>
<published>2011-01-03T19:57:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=83f0b79f43f2df35ac6fa9ba11973491e6a52b65'/>
<id>urn:sha1:83f0b79f43f2df35ac6fa9ba11973491e6a52b65</id>
<content type='text'>
Previously we emitted two newlines for export and unexport.
One newline for export and unexport is enough (and makes the scripts
look better and a tad smaller).

(Bitbake rev: ba060160fdf1278a273fb2b77d36b8c681807ecf)

Signed-off-by: Bernhard Reutner-Fischer &lt;rep.dot.nop@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>bitbake: Sync a load of whitespace and other non-functionality changes with bitbake uptream</title>
<updated>2011-01-04T14:46:54+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>rpurdie@linux.intel.com</email>
</author>
<published>2011-01-01T23:55:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0090a798eb868ebc926944eac2e6d4a5aff3e1b3'/>
<id>urn:sha1:0090a798eb868ebc926944eac2e6d4a5aff3e1b3</id>
<content type='text'>
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>bitbake: add optional expansion to getVarFlag()</title>
<updated>2010-12-14T22:36:19+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2010-12-10T15:30:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=80e6408b9f0a07e192696a2c2d371b258b4b187d'/>
<id>urn:sha1:80e6408b9f0a07e192696a2c2d371b258b4b187d</id>
<content type='text'>
Add a parameter to getVarFlag() to auto-expand the value of the flag. This
makes getVarFlag() more consistent with getVar(), and allows expansion of
vardeps and vardepsexclude (which has been done in this commit).

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>bitbake: allow excluding dependencies of variables</title>
<updated>2010-12-14T22:35:50+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2010-12-10T14:29:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a52e4063f4da3ac377959bbd1bea425c9a466df9'/>
<id>urn:sha1:a52e4063f4da3ac377959bbd1bea425c9a466df9</id>
<content type='text'>
Adds a vardepsexclude flag that can be used to exclude a dependency of
a variable (the opposite of vardeps). This will allow the exclusion of
variables from the hash generation much more selectively than blanket
whitelisting using BB_HASHBASE_WHITELIST.

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>bitbake: Overhaul environment handling</title>
<updated>2010-12-09T13:16:14+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>rpurdie@linux.intel.com</email>
</author>
<published>2010-11-28T17:39:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0ba9a9fffee966ec912eec5fd52c468338560e6a'/>
<id>urn:sha1:0ba9a9fffee966ec912eec5fd52c468338560e6a</id>
<content type='text'>
Currently, anything whitelisted in the environment makes it into the worker
processes. This is undesireable and the worker environment should be as
clean as possible. This patch adapts bitbake sosme variables are loaded into
bitbake's datastore but not exported by default. Any variable can be exported
by setting its export flag.

Currently, this code only finalises the environment in he worker as doing so
in the server means variables are unavailable in the worker. If we switch
back to fork() calls instead of exec() this code will need revisting.

Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>bitbake/data.py: Allow variables to suplement dependencies using the vardep flag</title>
<updated>2010-09-13T11:16:46+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>rpurdie@linux.intel.com</email>
</author>
<published>2010-09-13T11:16:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4aec2155a5f0ac051e29ad8a749c04fd37c47643'/>
<id>urn:sha1:4aec2155a5f0ac051e29ad8a749c04fd37c47643</id>
<content type='text'>
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>bitbake/data.py: Add emit_func() and generate_dependencies() functions</title>
<updated>2010-08-31T11:47:41+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>rpurdie@linux.intel.com</email>
</author>
<published>2010-08-03T13:30:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=332c33af188c14dd0051d8a45fe0ad680611db69'/>
<id>urn:sha1:332c33af188c14dd0051d8a45fe0ad680611db69</id>
<content type='text'>
These functions allow generation of dependency data between funcitons and
variables allowing moves to be made towards generating checksums and allowing
use of the dependency information in other parts of bitbake.

Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
</feed>
