From 43ad3f54eabc5a7c5086a2a551224cb817c167b8 Mon Sep 17 00:00:00 2001 From: "rpjday@crashcourse.ca" Date: Fri, 3 Apr 2020 08:01:03 -0400 Subject: 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 Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index aca750fd47..deeb358e0b 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1941,9 +1941,9 @@ The SRC_URI 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 SRC_URI. - Rather than hard-code these paths, use + Rather than hard-code these values, use ${PV}, which causes the fetch process to use the version specified in the recipe filename. @@ -1954,13 +1954,13 @@ Here is a simple example from the - meta/recipes-devtools/cdrtools/cdrtools-native_3.01a20.bb + meta/recipes-devtools/strace/strace_5.5.bb recipe where the source comes from a single tarball. Notice the use of the PV variable: - SRC_URI = "ftp://ftp.berlios.de/pub/cdrecord/alpha/cdrtools-${PV}.tar.bz2" + SRC_URI = "https://strace.io/files/${PV}/strace-${PV}.tar.xz \ -- cgit v1.2.3-54-g00ecf