From 34d1994b9bc47b22e219e93a3e1e27fc2cba41a6 Mon Sep 17 00:00:00 2001
From: Holger Hans Peter Freyther <zecke@selfish.org>
Date: Thu, 5 Jan 2006 20:26:12 +0000
Subject: bitbake/doc/manual:     -Mention the new require keyword

---
 doc/manual/usermanual.xml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/manual/usermanual.xml b/doc/manual/usermanual.xml
index b96863c03..277e61510 100644
--- a/doc/manual/usermanual.xml
+++ b/doc/manual/usermanual.xml
@@ -138,6 +138,12 @@ will be introduced.</para>
                 <title>Inclusion</title>
                 <para>Next, there is the <literal>include</literal> directive, which causes BitBake to parse in whatever file you specify, and insert it at that location, which is not unlike <command>make</command>.  However, if the path specified on the <literal>include</literal> line is a relative path, BitBake will locate the first one it can find within <envar>BBPATH</envar>.</para>
             </section>
+            <section>
+                <title>Requiring Inclusion</title>
+                <para>In contrast to the <literal>include</literal> directive, <literal>require</literal> will
+raise an ParseError if the to be included file can not be found. Otherwise it will behave just like the <literal>
+include</literal> directive.</para>
+            </section>
             <section>
                 <title>Python variable expansion</title>
                 <para><screen><varname>DATE</varname> = "${@time.strftime('%Y%m%d',time.gmtime())}"</screen></para>
-- 
cgit 1.2.3-korg