summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-03-19 06:51:41 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-25 12:29:43 +0000
commit46a4fb250e12d9afaac7d6b4c1ac799f26971845 (patch)
treef297a97b90cae9c2ac06cbd31e3ca00a7cf49151 /documentation
parentd8b69fb4de28d917839abfbad6287b45febf4fdd (diff)
downloadpoky-46a4fb250e12d9afaac7d6b4c1ac799f26971845.tar.gz
dev-manual: Read-thru edits for "Using an External SCM"
(From yocto-docs rev: 37a53af6448f10e8b8f7104295c4e927480312c5) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml17
1 files 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 @@
5369 <title>Using an External SCM</title> 5369 <title>Using an External SCM</title>
5370 5370
5371 <para> 5371 <para>
5372 If you're working on a recipe that pulls from an external Source Code Manager (SCM), it 5372 If you're working on a recipe that pulls from an external Source
5373 is possible to have the OpenEmbedded build system notice new recipe changes added to the 5373 Code Manager (SCM), it is possible to have the OpenEmbedded build
5374 SCM and then build the resulting package that depends on the new recipes by using the latest 5374 system notice new recipe changes added to the SCM and then build
5375 versions. 5375 the resulting packages that depend on the new recipes by using
5376 This only works for SCMs from which it is possible to get a sensible revision number for changes. 5376 the latest versions.
5377 Currently, you can do this with Apache Subversion (SVN), Git, and Bazaar (BZR) repositories. 5377 This only works for SCMs from which it is possible to get a
5378 sensible revision number for changes.
5379 Currently, you can do this with Apache Subversion (SVN), Git, and
5380 Bazaar (BZR) repositories.
5378 </para> 5381 </para>
5379 5382
5380 <para> 5383 <para>
@@ -5384,7 +5387,7 @@
5384 <literallayout class='monospaced'> 5387 <literallayout class='monospaced'>
5385 SRCREV_pn-&lt;PN&gt; = "${AUTOREV}" 5388 SRCREV_pn-&lt;PN&gt; = "${AUTOREV}"
5386 </literallayout> 5389 </literallayout>
5387 where <ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink> 5390 <ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink>
5388 is the name of the recipe for which you want to enable automatic source 5391 is the name of the recipe for which you want to enable automatic source
5389 revision updating. 5392 revision updating.
5390 </para> 5393 </para>