diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml index d7d6c92ee8..fbffade348 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml @@ -1065,13 +1065,41 @@ Deleting a Task - As well as being able to add tasks, tasks can also be deleted. - This is done simply with deltask command. + As well as being able to add tasks, you can delete them. + Simply use the deltask command to + delete a task. For example, to delete the example task used in the previous sections, you would use: deltask printdate + If you delete a task using the deltask + command and the task has dependencies, the dependencies are + not reconnected. + For example, suppose you have three tasks named + do_a, do_b, and + do_c. + Furthermore, do_c is dependent on + do_b, which in turn is dependent on + do_a. + Given this scenario, if you use deltask + to delete do_b, the implicit dependency + relationship between do_c and + do_a through do_b + no longer exists, and do_c dependencies + are not updated to include do_a. + Thus, do_c is free to run before + do_a. + + + + If you want dependencies such as these to remain intact, use + the noexec varflag to disable the task + instead of using the deltask command to + delete it: + + do_b[noexec] = "1" +