diff options
| author |   Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-03-19 06:51:41 -0600 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-03-25 12:29:43 +0000 |
| commit | 46a4fb250e12d9afaac7d6b4c1ac799f26971845 (patch) | |
| tree | f297a97b90cae9c2ac06cbd31e3ca00a7cf49151 /documentation | |
| parent | d8b69fb4de28d917839abfbad6287b45febf4fdd (diff) | |
| download | openembedded-core-contrib-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.xml | 17 |
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 @@ <title>Using an External SCM</title> <para> - 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. </para> <para> @@ -5384,7 +5387,7 @@ <literallayout class='monospaced'> SRCREV_pn-<PN> = "${AUTOREV}" </literallayout> - where <ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink> + <ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink> is the name of the recipe for which you want to enable automatic source revision updating. </para> |