yocto-project-qs: Updates to how to use local directories for source

The section that describes an efficient way to set up the
build system to look in local areas for tarballs needed updated
so that PREMIRRORS was not the focus.  The example used does
not even employ PREMIRRORS.  So I changed wording to support
the example.  I also added a mention of the PREMIRRORS variable
and a linked reference to it for more information.

(From yocto-docs rev: 7966942e2dfad85c2eb9480d7f706355871c40ab)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 20 insertions, 10 deletions

diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index f0d3dad..a1c714e 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -818,17 +818,19 @@
         </para>
 
         <para>
-            A good deal that goes into a Yocto Project build is simply downloading all of the source
-            tarballs.
-            Maybe you have been working with another build system (OpenEmbedded or Angstrom) for which
-            you've built up a sizable directory of source tarballs.
-            Or perhaps someone else has such a directory for which you have read access.
-            If so, you can save time by adding the <filename>PREMIRRORS</filename>
-            statement to your configuration file so that the build process checks
-            local directories first for existing tarballs before checking the
+            A good deal that goes into a Yocto Project build is simply
+            downloading all of the source tarballs.
+            Maybe you have been working with another build system
+            (OpenEmbedded or Angstrom) for which you have built up a sizable
+            directory of source tarballs.
+            Or, perhaps someone else has such a directory for which you have
+            read access.
+            If so, you can save time by adding statements to your
+            configuration file so that the build process checks local
+            directories first for existing tarballs before checking the
             Internet.
-            Here is an efficient way to set it up in your <filename>local.conf</filename>
-            file:
+            Here is an efficient way to set it up in your
+            <filename>local.conf</filename> file:
             <literallayout class='monospaced'>
      SOURCE_MIRROR_URL ?= "file:///home/you/your-download-dir/"
      INHERIT += "own-mirrors"
@@ -836,6 +838,14 @@
      # BB_NO_NETWORK = "1"
             </literallayout>
         </para>
+
+        <para>
+            You can also use the
+            <ulink url='&YOCTO_DOCS_REF_URL;#var-PREMIRRORS'><filename>PREMIRRORS</filename></ulink>
+            variable.
+            For an example, see the variable's glossary entry in the
+            Yocto Project Reference Manual.
+        </para>
     </section>
 
     <section id='building-the-image'>