ref-manual: Edits to the "source" section of yp dev environment

Fixes [YOCTO #2808]

I updated the "Sources" section with review comments from
Paul.  The figure needed changed as well as some text changes.

(From yocto-docs rev: 0a44dbdebce50fb599b8dcb2f17adc76f9fb862c)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-07-17 18:19:16 +03:00 committed by Richard Purdie
parent dc7f6e7d30
commit 69b317f38a
2 changed files with 9 additions and 7 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 40 KiB

View File

@ -641,9 +641,8 @@
A good method for using a download directory is to have
<filename>DL_DIR</filename> point to an area outside of your
Build Directory.
Doing so allows you to safely delete the Build Directory's
<filename>/work/tmp</filename> directory if needed without fear
of removing any downloaded source file.
Doing so allows you to safely delete the Build Directory
if needed without fear of removing any downloaded source file.
</para>
<para>
@ -675,7 +674,7 @@
Local projects are custom bits of software the user provides.
These bits reside somewhere local to a project - perhaps
a directory into which the user checks in items (e.g.
a local directory that contains tarballs or repositories
a local directory containing a development source tree
used by the group).
</para>
@ -684,11 +683,10 @@
is to use the
<link linkend='ref-classes-externalsrc'><filename>externalsrc.bbclass</filename></link>
class to include local project.
You use a recipe's append file to override or instruct the
You use either the <filename>local.conf</filename> or a
recipe's append file to override or set the
recipe to point to the local directory on your disk to pull
in the whole source tree.
Should you ever need to override that, you can use the
Build Directory's <filename>local.conf</filename> file.
</para>
<para>
@ -725,6 +723,10 @@
<para>
Two kinds of mirrors exist: pre-mirrors and regular mirrors.
The <link linkend='var-PREMIRRORS'><filename>PREMIRRORS</filename></link>
and
<link linkend='var-MIRRORS'><filename>MIRRORS</filename></link>
variables point to these, respectively.
BitBake checks pre-mirrors before looking upstream for any
source files.
Pre-mirrors are appropriate when you have a shared directory