diff options
authorRolf Leggewie <oe-devel@rolf.leggewie.biz>2008-02-26 14:49:29 +0000
committerRolf Leggewie <oe-devel@rolf.leggewie.biz>2008-02-26 14:49:29 +0000
commit27689da47c30f984ac637f14743ae3918003a68f (patch)
parentabfb4d431fb2611e962442de19d38cfd258aa584 (diff)
common_use_cases.xml: add a chapter about how to use svn/cvs in a bb file properly.
1 files changed, 22 insertions, 1 deletions
diff --git a/usermanual/chapters/common_use_cases.xml b/usermanual/chapters/common_use_cases.xml
index 775b089f50..6505565886 100644
--- a/usermanual/chapters/common_use_cases.xml
+++ b/usermanual/chapters/common_use_cases.xml
@@ -99,7 +99,28 @@ SRCDATE = "20061014"
<section id="commonuse_new_package">
<title>Adding a new Package</title>
- <para>This section is a stub, help us by expanding it</para>
+ <para>This section is a stub, help us by expanding it. Learn by example, go through the
+ recipes that are already there and mimic them to do what you want.</para>
+ <section>
+ <title>building from unstable source code</title>
+ <para>Building against the latest, bleeding-edge source has some intricacies of its own.
+ For one, it is desirable to pin down a souce code revision that is known to build to
+ prevent random breakage in OE at the most inopportune time for all OE users. Here is
+ how to do that properly.
+ <itemizedlist>
+ <listitem>for svn: add 'PV = "1.1+svnr${SRCREV}"' to your bb file.</listitem>
+ <listitem>for cvs: add 'PV = "1.1+cvs${SRCREV}"' to your bb file.</listitem>
+ </itemizedlist>
+ Accompany either with an entry to conf/sane-srcrevs.inc for a revision that you know
+ builds successfully.
+ </para>
+ <para>
+ If you really absolutely have to follow the latest commits, you can do that by adding
+ 'SRCREV_pn-linux-davinci ?= ${AUTOREV}' to your local.conf, for example. In this case,
+ you'd build against the most recent and unstable source for the pn-linux-davinci package.
+ </para>
+ </section>
<section id="commonuse_new_image">