dev-manual: use "strace" for PV example, not cdrtools

Section 3.3.5, "Fetching Code", uses the cdrtools recipe as an example
for showing the use of PV, but that's a bad example since the current
cdrtools recipe file contains:

  SRC_URI = " \
  ${SOURCEFORGE_MIRROR}/project/cdrtools/cdrtools-${REALPV}.tar.bz2 \
  ...

  PV = "3.01a31+really3.01"
  REALPV = "3.01"

which is not exactly the point the dev manual is trying to make, so
replace with simpler strace recipe.

(From yocto-docs rev: d865b0288a4162a8d4df9a2abde43875e3dc2ced)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
rpjday@crashcourse.ca
2020-04-03 08:01:03 -04:00
committed by Richard Purdie
parent 45792835fe
commit 43ad3f54ea

View File

@@ -1941,9 +1941,9 @@
<para>
The <filename>SRC_URI</filename> variable in your recipe must
define each unique location for your source files.
It is good practice to not hard-code pathnames in an URL used
It is good practice to not hard-code version numbers in a URL used
in <filename>SRC_URI</filename>.
Rather than hard-code these paths, use
Rather than hard-code these values, use
<filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PV'><filename>PV</filename></ulink><filename>}</filename>,
which causes the fetch process to use the version specified in
the recipe filename.
@@ -1954,13 +1954,13 @@
<para>
Here is a simple example from the
<filename>meta/recipes-devtools/cdrtools/cdrtools-native_3.01a20.bb</filename>
<filename>meta/recipes-devtools/strace/strace_5.5.bb</filename>
recipe where the source comes from a single tarball.
Notice the use of the
<ulink url='&YOCTO_DOCS_REF_URL;#var-PV'><filename>PV</filename></ulink>
variable:
<literallayout class='monospaced'>
SRC_URI = "ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-${PV}.tar.bz2"
SRC_URI = "https://strace.io/files/${PV}/strace-${PV}.tar.xz \
</literallayout>
</para>