ref-manual: Review edits added to do_patch task

Mentioned the role of SRC_URI earlier in the description as it is key.
Replaced "some_recipe" with "some_package" as the emphisis is not on
the recipe at that point in the example.

(From yocto-docs rev: f7f86941fdf866a693386335374f835078db3ddf)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 15 insertions, 8 deletions

diff --git a/documentation/ref-manual/ref-tasks.xml b/documentation/ref-manual/ref-tasks.xml
index 93ad692775..e6cf68670b 100644
--- a/documentation/ref-manual/ref-tasks.xml
+++ b/documentation/ref-manual/ref-tasks.xml
@@ -432,8 +432,16 @@
         </para>
 
         <para>
-            After fetching and unpacking source files, the build system locates
-            and applies patches to the source code.
+            After fetching and unpacking source files, the build system
+            uses the recipe's
+            <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>
+            statements to locate and apply patch files to the source code.
+            <note>
+                The build system uses the
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-FILESPATH'><filename>FILESPATH</filename></ulink>
+                variable to determine the default set of directories when
+                searching for patches.
+            </note>
             Patch files, by default, are <filename>*.patch</filename> and
             <filename>*.diff</filename> files created and kept in a
             subdirectory of the directory holding the recipe file.
@@ -451,10 +459,9 @@
         </para>
 
         <para>
-            The recipe for <filename>bluez5</filename> uses the
-            <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>
-            variable to point to the source and patch files needed to build
-            the recipe.
+            In the <filename>bluez5</filename> recipe, the
+            <filename>SRC_URI</filename> statements point to the source and
+            patch files needed to build the package.
             <note>
                 In the case for the <filename>bluez5_5.48.bb</filename>
                 recipe, the <filename>SRC_URI</filename> statements are from an
@@ -471,7 +478,7 @@
             patch file:
             <literallayout class='monospaced'>
      SRC_URI = " \
-          git://<replaceable>path_to_repo</replaceable>/<replaceable>some_recipe</replaceable> \
+          git://<replaceable>path_to_repo</replaceable>/<replaceable>some_package</replaceable> \
           file://<replaceable>file</replaceable>;apply=yes \
      "
             </literallayout>
@@ -485,7 +492,7 @@
             statement:
             <literallayout class='monospaced'>
      SRC_URI = " \
-          git://<replaceable>path_to_repo</replaceable>/<replaceable>some_recipe</replaceable> \
+          git://<replaceable>path_to_repo</replaceable>/<replaceable>some_package</replaceable> \
           file://<replaceable>path_to_lots_of_patch_files</replaceable> \
           file://<replaceable>path_to_lots_of_patch_files</replaceable>/<replaceable>patch_file5</replaceable>;apply=no \
      "