documentation/dev-manual: Fixed 6.0 to 6.0.1 for 1.1.1 release.

Needed to change the "6.0" occurences to "6.0.1" in the examples.

(From yocto-docs rev: d6b40b3b0e98eba7f3221e79cb9612f8f10bffaf)

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-01-10 19:05:05 -06:00 committed by Richard Purdie
parent 1cb265f575
commit b17aecd70a
2 changed files with 5 additions and 5 deletions

View File

@ -216,9 +216,9 @@
system in order to do any development using the Yocto Project.</para>
<para>The name of the top-level directory of the Yocto Project file structure
is derived from the Yocto Project release tarball.
For example, downloading and unpacking <filename>poky-edison-6.0.tar.bz2</filename>
For example, downloading and unpacking <filename>poky-edison-6.0.1.tar.bz2</filename>
results in a Yocto Project file structure whose Yocto Project source directory is named
<filename>poky-edison-6.0</filename>.
<filename>poky-edison-6.0.1</filename>.
If you create a Git repository, then you can name the repository anything you like.</para>
<para>You can find instruction on how to set up the Yocto Project files on your
host development system by reading
@ -233,9 +233,9 @@
You can create the Yocto Project build directory anywhere you want on your
development system.
Here is an example that creates the directory in <filename>mybuilds</filename>
and names the Yocto Project build directory <filename>YP-6.0</filename>:
and names the Yocto Project build directory <filename>YP-6.0.1</filename>:
<literallayout class='monospaced'>
$ source poky-edison-6.0/oe-init-build-env $HOME/mybuilds/YP-6.0
$ source poky-edison-6.0.1/oe-init-build-env $HOME/mybuilds/YP-6.0.1
</literallayout>
If you don't specifically name the directory, BitBake creates it
in the current directory and uses the name <filename>build</filename>.

View File

@ -79,7 +79,7 @@
into the current working directory and sets up the Yocto Project file structure
with a top-level directory named <filename>poky-1.1.1</filename>:
<literallayout class='monospaced'>
$ tar xfj poky-edison-6.0.tar.bz2
$ tar xfj poky-edison-6.0.1.tar.bz2
</literallayout></para>
<para>This method does not produce a Git repository.
Instead, you simply end up with a local snapshot of the