1 files changed, 14 insertions, 1 deletions

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 857f8b279c..4cc647fe4b 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -1686,7 +1686,7 @@
                             recipe is built.
                             In this example, <filename>mytask</filename> is run
                             at an unspecified time relative to other tasks within
-                            the recipe, since "after" is not used.
+                            the recipe, since <filename>after</filename> is not used.
                             </para></listitem>
                         <listitem><para>
                             The directive
@@ -1773,6 +1773,19 @@
             </para>
 
             <para>
+                The "recrdeptask" flag is most commonly used in high-level
+                recipes that need to wait for some task to finish "globally".
+                For example, <filename>image.bbclass</filename> has the following:
+                <literallayout class='monospaced'>
+     do_rootfs[recrdeptask] += "do_packagedata"
+                </literallayout>
+                This statement says that the <filename>do_packagedata</filename>
+                task of all recipes reachable (by way of dependencies) from the
+                image recipe must run before the <filename>do_rootfs</filename>
+                task can run.
+            </para>
+
+            <para>
                 You might want to not only have BitBake look for
                 dependencies of those tasks, but also have BitBake look
                 for build-time and runtime dependencies of the dependent