sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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>
This commit is contained in:
Scott Rifenbark 2014-03-19 06:51:41 -06:00 committed by Richard Purdie
parent d8b69fb4de
commit 46a4fb250e
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -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-&lt;PN&gt; = "${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>