<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/classes/rm_work.bbclass, branch python3</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=python3</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=python3'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2016-01-11T23:26:29+00:00</updated>
<entry>
<title>classes: Fix do_rootfs references</title>
<updated>2016-01-11T23:26:29+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2016-01-06T22:57:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3341f3fbee818a0bd62620b8bc34230b03c0689c'/>
<id>urn:sha1:3341f3fbee818a0bd62620b8bc34230b03c0689c</id>
<content type='text'>
After the separation of do_rootfs, some rootfs references need changing
to image_complete.

(From OE-Core rev: 59a5f596ca29b1eb8283706e3c60fbb39f9c2c23)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rm_work.bbclass: Exclude do_rootfs stamp removal</title>
<updated>2015-11-16T11:39:33+00:00</updated>
<author>
<name>Jate Sujjavanich</name>
<email>jatedev@gmail.com</email>
</author>
<published>2015-10-30T14:56:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=efc07c293695c21329442d69fe34411027416188'/>
<id>urn:sha1:efc07c293695c21329442d69fe34411027416188</id>
<content type='text'>
This prevents unneeded rootfs rebuilds if the metadata has not changed
while using rm_work.

(From OE-Core rev: 7550b13786caa68a9944cd802eb970acbd17e754)

Signed-off-by: Jate Sujjavanich &lt;jatedev@gmail.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel/rm_work: Improve interaction</title>
<updated>2015-05-15T16:44:59+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2015-05-14T09:31:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f5f2467e4bdd1a3fda9b443712d32502645ebe3e'/>
<id>urn:sha1:f5f2467e4bdd1a3fda9b443712d32502645ebe3e</id>
<content type='text'>
The do_shared_workdir task does leave behind the necessary information in
shared-work after it completes. We don't make this a "full" sstate task
however since that means tarring up and copying what is usually a large
amount of data which would be better extracted straight from the original
SCM.

The issue with rm_work occurs since it removes the do_shared_workdir stamp
meaning subsequent builds will add it back if they need to touch any kernel
modules for example. This ends up triggering a near enough complete kernerl
rebuild since if configure reruns, populate_sysroot has to rerun.

This change promotes the task to have a "setscene" variant but it doesn't use
any of the sstate class lifting to generate the sstate file. The sstate function
will therefore never get called since the sstate object will never exist.

We can add the task to the list of tasks rm_work promotes to a setscene variant
and unwanted rebuilds of the kernel should be avoided.

(From OE-Core rev: 55b4f7fd217f0c65d457c731150340c18fb3fa19)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rm_work: Fix RM_WORK_EXCLUDE for image/sdk recipes</title>
<updated>2015-01-08T09:24:47+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2015-01-07T23:45:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2aa210cbc51df18e74eb04ece9ec5cd29057d2c2'/>
<id>urn:sha1:2aa210cbc51df18e74eb04ece9ec5cd29057d2c2</id>
<content type='text'>
A previous change meant image/sdk recipes were removed unconditionally
by the class and did not respect RM_WORK_EXCLUDE. This fixes that
problem.

[YOCTO #7114]

(From OE-Core rev: 050de16968fe6efeba5d64761b11512549e9fdc2)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rm_work: Speed up rootfs/populate_sdk removal</title>
<updated>2014-10-30T13:01:21+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2014-10-24T14:14:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6476f0bf3dc189948fafedf6be112f875e42225f'/>
<id>urn:sha1:6476f0bf3dc189948fafedf6be112f875e42225f</id>
<content type='text'>
Commands like bitbake X -c rootfs or bitbake X -c populate_sdk do not
trigger rm_work to clean up the directories afterwards since it
traditionally hooks onto do_build. This change means those two tasks now
clean up after themselves. We use the cleandirs function attribute to
handle this.

[YOCTO #6413]

(From OE-Core rev: 6bf06d80c2ce03dfdedac5ad8cf42ef8e36b0ecb)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rm_work.bbclass: ignore failure for removing pseudo folder</title>
<updated>2013-05-24T13:14:48+00:00</updated>
<author>
<name>Ming Liu</name>
<email>ming.liu@windriver.com</email>
</author>
<published>2013-05-23T07:33:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b08958bc22f67dff25390bd96a697a94915ed9bb'/>
<id>urn:sha1:b08958bc22f67dff25390bd96a697a94915ed9bb</id>
<content type='text'>
When building over NFS2/3 server, removal of pseudo folders will fail in
some cases for there are files in it still used by pseudo daemon, thus
cause ".nfsXXXXX" files generated which can't be removed by clients. This
will lead rm_work task fo fail.

These failures could be safely ignored because ".nfsXXXXX" files would be
automatically cleared by NFS server when no clients keep opening them.

[YOCTO #4531]
[ CQID: WIND00412051 ]

(From OE-Core rev: 9742e866f545bc0d04aca697b541ed88f4e1764a)

Signed-off-by: Ming Liu &lt;ming.liu@windriver.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>classes/rm_work: rename RM_WORK_WHITELIST to RM_WORK_EXCLUDE</title>
<updated>2013-03-26T21:19:51+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2013-03-26T17:47:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bdca49274173153b1b0a72887de6321b4756b684'/>
<id>urn:sha1:bdca49274173153b1b0a72887de6321b4756b684</id>
<content type='text'>
This really functions as a blacklist, not a whitelist, since we are
listing recipes to exclude. To avoid any possibility of confusion, since
this was a recent addition, rename the variable.

(From OE-Core rev: 4d56de8018d550b3d181d451900cbfb698d64141)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rm_work.bbclass: inhibit rm_work per recipe</title>
<updated>2013-03-18T13:18:21+00:00</updated>
<author>
<name>Chen Qi</name>
<email>Qi.Chen@windriver.com</email>
</author>
<published>2013-03-13T07:01:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=83409910dd3a31589ca9ea4172a70f0bcd877d8f'/>
<id>urn:sha1:83409910dd3a31589ca9ea4172a70f0bcd877d8f</id>
<content type='text'>
Use RM_WORK_WHITELIST to inhibit rm_work per recipe. In this way,
one can use rm_work for the most of the recipes but still keep the
work area for the recipe(s) one is working on.

As an example, the following settings in local.conf will inhibit
rm_work for icu-native, icu and busybox.
    INHERIT += "rm_work"
    RM_WORK_WHITELIST += "icu-native icu busybox"

If we comment out the RM_WORK_WHITELIST line and do a rebuild, the
working area of these recipes will be cleaned up.

[YOCTO #3675]

(From OE-Core rev: 6c930c3c06f2e698540626c87bd7f7f571df35ef)

Signed-off-by: Chen Qi &lt;Qi.Chen@windriver.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rm_work: remove package and packages-split dirs</title>
<updated>2013-03-02T12:56:53+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>martin.jansa@gmail.com</email>
</author>
<published>2013-03-02T00:02:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=f090c1523f6fd600dde01e53250f9b1ea79219c6'/>
<id>urn:sha1:f090c1523f6fd600dde01e53250f9b1ea79219c6</id>
<content type='text'>
* as described in
  http://git.openembedded.org/openembedded-core/commit/?id=6107ee294afde395e39d084c33e8e94013c625a9

(From OE-Core rev: 4067afcda78d17058f2aa8d7f82173d181e0aae4)

Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Various typoes fixed, all comments or output strings.</title>
<updated>2012-03-26T11:13:05+00:00</updated>
<author>
<name>Robert P. J. Day</name>
<email>rpjday@crashcourse.ca</email>
</author>
<published>2012-03-25T11:46:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=951aa5ea1f1e23460bb3607e5442a2a2bc499e6f'/>
<id>urn:sha1:951aa5ea1f1e23460bb3607e5442a2a2bc499e6f</id>
<content type='text'>
Typoes fixed: "enviroment", "editted", "spliting", "scheulder".

(From OE-Core rev: 17e981a857a51b0bec08c929e8539d36d83874b6)

Signed-off-by: Robert P. J. Day &lt;rpjday@crashcourse.ca&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
