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

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 <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2012-09-21 07:02:00 -07:00 committed by Richard Purdie
parent 249869ec2f
commit 9bc3b44866
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1716,8 +1716,9 @@
<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 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.
</para>
@ -1730,7 +1731,7 @@
SRCREV_pn-&lt;PN&gt; = "${AUTOREV}"
</literallayout>
where <filename>PN</filename>
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.
</para>
</section>