From 9bc3b4486665d8e51cafdb717d69f0a01537b33a Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 21 Sep 2012 07:02:00 -0700 Subject: documentation/dev-manual/dev-manual-common-tasks.xml: external SCM Update Updated the section "Using an External SCM." This section was written so that PN was refering to a package instead of correctly refering to the recipe. (From yocto-docs rev: 2bf44cf78bef08d2dd4d9e596100900913777d60) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml') diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index e456d540a0..b42a09bf2b 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1716,8 +1716,9 @@ If you're working on a recipe that pulls from an external Source Code Manager (SCM), it - is possible to have the OpenEmbedded build system notice new changes added to the - SCM and then build the package that depends on them using the latest version. + is possible to have the OpenEmbedded build system notice new recipe changes added to the + SCM and then build the resulting package that depends on the new recipes by using the latest + versions. This only works for SCMs from which it is possible to get a sensible revision number for changes. Currently, you can do this with Apache Subversion (SVN), Git, and Bazaar (BZR) repositories. @@ -1730,7 +1731,7 @@ SRCREV_pn-<PN> = "${AUTOREV}" where PN - is the name of the package for which you want to enable automatic source + is the name of the recipe for which you want to enable automatic source revision updating. -- cgit v1.2.3-54-g00ecf