[gnome-continuous-yocto/gnomeostree-3.28-rocko: 7545/8267] ref-manual: Updated SSTATE_SCAN_FILES variable description

[Emmanuele Bassi <ebassi src gnome org>]

commit 79f860e146a35a29f27958b5a02f8c926d0f807b
Author: Kristi Rifenbark <kristi rifenbark gmail com>
Date:   Fri Aug 18 14:19:15 2017 -0700

    ref-manual: Updated SSTATE_SCAN_FILES variable description
    
    (From yocto-docs rev: 190b257e788d7f6f2f87e4e8c031bcda4a9f6d46)
    
    Signed-off-by: Kristi Rifenbark <kristi rifenbark gmail com>
    Signed-off-by: Richard Purdie <richard purdie linuxfoundation org>

 documentation/ref-manual/ref-variables.xml |   14 ++++++++++----
 1 files changed, 10 insertions(+), 4 deletions(-)
---
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index f2414c5..0289ad1 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -12963,17 +12963,23 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                 <para role="glossdeffirst">
 <!--                <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
                     Controls the list of files the OpenEmbedded build system
-                    scans for hardcoded installation paths.
+                    scans for hardcoded installation paths. The variable uses a
+                    space-separated list of filenames (not paths) with standard
+                    wildcard characters allowed.
                 </para>
 
                 <para>
                     During a build, the OpenEmbedded build system creates a
                     shared state (sstate) object during the first stage of
-                    preparing the sysroots.
-                    During the build, the object is scanned for hardcoded paths
-                    for original installation locations.
+                    preparing the sysroots. That object is scanned for
+                    hardcoded paths for original installation locations.
                     The list of files that are scanned for paths is controlled
                     by the <filename>SSTATE_SCAN_FILES</filename> variable.
+                    Typically, recipes add files they want to be scanned to the
+                    value of <filename>SSTATE_SCAN_FILES</filename> rather than
+                    the variable being comprehensively set. The
+                    <link linkend='ref-classes-sstate'><filename>sstate</filename></link>
+                    class specifies the default list of files.
                 </para>
 
                 <para>