From 46a4fb250e12d9afaac7d6b4c1ac799f26971845 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 19 Mar 2014 06:51:41 -0600 Subject: dev-manual: Read-thru edits for "Using an External SCM" (From yocto-docs rev: 37a53af6448f10e8b8f7104295c4e927480312c5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 9e269c1cdb..23ea2df38e 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -5369,12 +5369,15 @@ Using an External SCM - 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 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. + 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 recipe changes added to the SCM and then build + the resulting packages that depend 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. @@ -5384,7 +5387,7 @@ SRCREV_pn-<PN> = "${AUTOREV}" - where PN + PN is the name of the recipe for which you want to enable automatic source revision updating. -- cgit v1.2.3-54-g00ecf