]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commitdiff
documentation/dev-manual/dev-manual-common-tasks.xml: note on readme
authorScott Rifenbark <scott.m.rifenbark@intel.com>
Tue, 4 Sep 2012 17:48:47 +0000 (10:48 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 14 Sep 2012 08:50:45 +0000 (09:50 +0100)
Added a note in the "Creating Layers" section noting that to be
Yocto Project compliant, a layer must contain a README file.  This
change was prompted by a discussion over the fact between Robert
P. J. Day and Mark Hatle.

(From yocto-docs rev: 2e073763a81125699a2d962031ca29ca64c81595)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
documentation/dev-manual/dev-manual-common-tasks.xml

index fe198119b7e3a611bbd226e2289119b2f64d0ce8..bdf59de8a6cd1a37f819a46c40703446d9a6e295 100644 (file)
                         If the layer adds distro policy, add the distro configuration in a
                         <filename>conf/distro/</filename> file with the layer.
                         If the layer introduces new recipes, put the recipes you need in 
-                        <filename>recipes-*</filename> subdirectories within the layer.</para></listitem>
+                        <filename>recipes-*</filename> subdirectories within the layer.
+                        <note>In order to be compliant with the Yocto Project, a layer must contain
+                            a <ulink url='&YOCTO_DOCS_BSP_URL;#bsp-filelayout-readme'>README file.</ulink>
+                            </note></para></listitem>
                 </orderedlist>
             </para>