documentation/dev-manual: Edits to clarify YP files

These edits help explain the differences between local YP files
created through a tarball extraction vs cloning a Git repository.

(From yocto-docs rev: ed368800c3e9ece71d27d6d690f0ddc264a4c2da)

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
2012-02-02 14:18:55 -06:00
committed by Richard Purdie
parent 11c290c3cf
commit 9cfbefcc3d
2 changed files with 18 additions and 4 deletions

View File

@@ -63,7 +63,9 @@
for the supported distributions.</para></listitem>
<listitem id='local-yp-release'><para><emphasis>Yocto Project Release:</emphasis>
You need a release of the Yocto Project.
You can get set up with local Yocto Project files one of two ways depending on whether you
You can get set up with local
<link linkend='yocto-project-files'>Yocto Project Files</link> one of two ways
depending on whether you
are going to be contributing back into the Yocto Project source repository or not.
<note>
Regardless of the method you use, this manual refers to the resulting
@@ -89,7 +91,9 @@
back into the Yocto Project, you should use Git commands to set up a local
Git repository of the Yocto Project files.
Doing so creates a Git repository with a complete history of changes and allows
you to easily submit your changes upstream to the project.</para>
you to easily submit your changes upstream to the project.
Because you cloned the repository, you have access to all the Yocto Project development
branches and tag names used in the upstream repository.</para>
<para>The following transcript shows how to clone the Yocto Project files'
Git repository into the current working directory.
The command creates the repository in a directory named <filename>poky</filename>.