diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2015-05-22 09:42:34 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-05-22 16:51:57 +0100 |
commit | 5ea3a206bb5beef4c12d56d9e42e29d324a08e16 (patch) | |
tree | dfe4b312e4f05ac09d8011f209e91bdd2d704c7e /doc/bitbake-user-manual | |
parent | d9811231b4c8211446bd9275084c26a4718cd175 (diff) | |
download | bitbake-5ea3a206bb5beef4c12d56d9e42e29d324a08e16.tar.gz |
bitbake-user-manual: Updated "Delete a Task" section for broken deps
Fixes [YOCTO #7803]
I added information for the scenario where deleting a task using the
deltask command could "break" implicit dependencies.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'doc/bitbake-user-manual')
-rw-r--r-- | doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 32 |
1 files changed, 30 insertions, 2 deletions
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml index d7d6c92ee..fbffade34 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml @@ -1065,13 +1065,41 @@ <title>Deleting a Task</title> <para> - As well as being able to add tasks, tasks can also be deleted. - This is done simply with <filename>deltask</filename> command. + As well as being able to add tasks, you can delete them. + Simply use the <filename>deltask</filename> command to + delete a task. For example, to delete the example task used in the previous sections, you would use: <literallayout class='monospaced'> deltask printdate </literallayout> + If you delete a task using the <filename>deltask</filename> + command and the task has dependencies, the dependencies are + not reconnected. + For example, suppose you have three tasks named + <filename>do_a</filename>, <filename>do_b</filename>, and + <filename>do_c</filename>. + Furthermore, <filename>do_c</filename> is dependent on + <filename>do_b</filename>, which in turn is dependent on + <filename>do_a</filename>. + Given this scenario, if you use <filename>deltask</filename> + to delete <filename>do_b</filename>, the implicit dependency + relationship between <filename>do_c</filename> and + <filename>do_a</filename> through <filename>do_b</filename> + no longer exists, and <filename>do_c</filename> dependencies + are not updated to include <filename>do_a</filename>. + Thus, <filename>do_c</filename> is free to run before + <filename>do_a</filename>. + </para> + + <para> + If you want dependencies such as these to remain intact, use + the <filename>noexec</filename> varflag to disable the task + instead of using the <filename>deltask</filename> command to + delete it: + <literallayout class='monospaced'> + do_b[noexec] = "1" + </literallayout> </para> </section> |