documentation/dev-manual/dev-manual-bsp-appendix.xml: Modified the setup section.

(From yocto-docs rev: 78224ffa3cfd5e110a2d2e43e8c84b259a84ee63)

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

1 files changed, 4 insertions, 44 deletions

diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml
index f3927c35d2..84fb541598 100644
--- a/documentation/dev-manual/dev-manual-bsp-appendix.xml
+++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml
@@ -18,55 +18,15 @@
     </itemizedlist>             
 </para>
 
-<section id='setting-up-yocto-project-app'>
-    <title>Setting Up Yocto Project</title>
+<section id='getting-local-yocto-project-files-and-bsp-files'>
+    <title>Getting Local Yocto Project Files and BSP Files</title>
 
     <para>
         You need to have the Yocto Project files available on your host system.  
         You can get files through tarball extraction or by cloning the <filename>poky</filename>
         Git repository.  
-        Typically, cloning the Git repository is the method to use.  
-        This allows you to maintain a complete history of changes and facilitates you 
-        contributing back to the Yocto Project.  
-        However, if you just want a hierarchical file structure that contains the recipes
-        and metadata that let you develop you can download tarballs from the 
-        <ulink url='http://yoctoproject.org/download'>download page</ulink>.
-    </para>
-
-    <para>
-        Regardless of the method you use this manual will refer to the resulting 
-        hierarchical set of files as "the local Yocto Project files."
-    </para>
-
-    <para>
-        [WRITER'S NOTE: I need to substitute correct and actual filenames for the 
-        1.1 release throughout this example once they become available.]
-    </para>
-
-    <para>  
-        If you download a tarball you can extract it into any directory you want using the 
-        tar command.  
-        For example, the following command extracts the Yocto Project 1.1 release tarball 
-        into the current working directory and sets up a file structure whose top-level 
-        directory is named <filename>poky-1.1</filename>:
-        <literallayout class='monospaced'>
-     $ tar xfj poky-1.1.tar.bz2
-        </literallayout>
-    </para>
-
-    <para>
-        The following transcript shows how to clone the <filename>poky</filename> Git repository
-        into the current working directory.  
-        The command creates the repository in a directory named <filename>poky</filename>:
-        <literallayout class='monospaced'>
-     $ git clone git://git.yoctoproject.org/poky
-     Initialized empty Git repository in /home/scottrif/poky/.git/
-     remote: Counting objects: 107624, done.
-     remote: Compressing objects: 100% (37128/37128), done.
-     remote: Total 107624 (delta 73393), reused 99851 (delta 67287)
-     Receiving objects: 100% (107624/107624), 69.74 MiB | 483 KiB/s, done.
-     Resolving deltas: 100% (73393/73393), done.
-        </literallayout>
+        See the <xref linkend='getting-setup'>Getting Setup</xref> earlier in this manual
+        for information on how to get these files.
     </para>
 
     <para>