dev-manual: Replaced release names and numbers with variables

In several examples, hardcoded versions of release names and
versions were being used.  I updated to use variables from
poky.ent so that examples would use most recent release.

(From yocto-docs rev: 53f8e92075cc34538f36d7fba392ea1ac9a6dd1f)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2017-09-21 13:15:21 -07:00
committed by Richard Purdie
parent b103ff6ba7
commit b673c3b990

View File

@@ -354,9 +354,9 @@
<listitem><para>
<emphasis>Find the Tarball:</emphasis>
Drill down to find the associated tarball.
For example, click on <filename>yocto-2.3</filename> to
view files associated with the Yocto Project 2.3
release (e.g. <filename>poky-pyro-17.0.0tar.bz2</filename>,
For example, click on <filename>yocto-&DISTRO;</filename> to
view files associated with the Yocto Project &DISTRO;
release (e.g. <filename>poky-&DISTRO_NAME_NO_CAP;-&POKYVERSION;.tar.bz2</filename>,
which is the released Poky tarball).
</para></listitem>
<listitem><para>
@@ -545,21 +545,22 @@
remotes/origin/pinky
remotes/origin/purple
remotes/origin/pyro
remotes/origin/rocko
</literallayout>
</para></listitem>
<listitem><para>
<emphasis>Checkout the Branch:</emphasis>
Checkout the development branch in which you want to work.
For example, to access the files for the Yocto Project
2.3 Release (Pyro), use the following command:
&DISTRO; Release (&DISTRO_NAME;), use the following command:
<literallayout class='monospaced'>
$ git checkout -b pyro origin/pyro
Branch pyro set up to track remote branch pyro from origin.
Switched to a new branch 'pyro'
$ git checkout -b &DISTRO_NAME_NO_CAP; origin/&DISTRO_NAME_NO_CAP;
Branch &DISTRO_NAME_NO_CAP; set up to track remote branch &DISTRO_NAME_NO_CAP; from origin.
Switched to a new branch '&DISTRO_NAME_NO_CAP;'
</literallayout>
The previous command checks out the "pyro" development
branch and reports that the branch is tracking the upstream
"origin/pyro" branch.</para>
The previous command checks out the "&DISTRO_NAME_NO_CAP;"
development branch and reports that the branch is tracking
the upstream "origin/&DISTRO_NAME_NO_CAP;" branch.</para>
<para>The following command displays the branches
that are now part of your local poky repository.
@@ -568,7 +569,7 @@
<literallayout class='monospaced'>
$ git branch
master
* pyro
* &DISTRO_NAME_NO_CAP;
</literallayout>
</para></listitem>
</orderedlist>
@@ -626,27 +627,29 @@
yocto-2.2
yocto-2.2.1
yocto-2.3
yocto-2.3.1
yocto-2.4
yocto_1.5_M5.rc8
</literallayout>
</para></listitem>
<listitem><para>
<emphasis>Checkout the Branch:</emphasis>
<literallayout class='monospaced'>
$ git checkout tags/2.2_M2 -b my_yocto_2.2_M2
Switched to a new branch 'my_yocto_2.2_M2'
$ git checkout tags/&DISTRO; -b my_yocto_&DISTRO;
Switched to a new branch 'my_yocto_&DISTRO;'
$ git branch
master
* my_yocto_2.2_M2
* my_yocto_&DISTRO;
</literallayout>
The previous command creates and checks out a local
branch named "my_yocto_2.2_M2", which is based on
branch named "my_yocto_&DISTRO;", which is based on
the commit in the upstream poky repository that has
the same tag.
In this example, the files you have available locally
as a result of the <filename>checkout</filename>
command are a snapshot of the
"morty" development branch at the point where
milestone two was reached.
"&DISTRO_NAME_NO_CAP;" development branch at the point
where Yocto Project &DISTRO; was released.
</para></listitem>
</orderedlist>
</para>