ref-manual: Re-ordered the classes that start with "D".

(From yocto-docs rev: e65278b9476681eb6f9c662993e110ee4422ebc7)

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 2013-12-05 13:06:21 -06:00 committed by Richard Purdie
parent 35dcd38287
commit 8f3ed72b06
1 changed files with 52 additions and 53 deletions

View File

@ -483,6 +483,16 @@
</para>
</section>
<section id='ref-classes-debian'>
<title>Debian Renaming - <filename>debian.bbclass</filename></title>
<para>
This class renames packages so that they follow the Debian naming
policy (i.e. <filename>eglibc</filename> becomes <filename>libc6</filename>
and <filename>eglibc-devel</filename> becomes <filename>libc6-dev</filename>.)
</para>
</section>
<section id='ref-classes-deploy'>
<title><filename>deploy.bbclass</filename></title>
@ -503,12 +513,15 @@
</para>
</section>
<section id='ref-classes-distrodata'>
<title><filename>distrodata.bbclass</filename></title>
<section id='ref-classes-devshell'>
<title>Developer Shell - <filename>devshell.bbclass</filename></title>
<para>
The Distribution Data (<filename>distrodata</filename>) class
provides for automatic checking for upstream recipe updates.
This class adds the <filename>devshell</filename> task.
Distribution policy dictates whether to include this class.
See the
"<ulink url='&YOCTO_DOCS_DEV_URL;#platdev-appdev-devshell'>Using a Development Shell</ulink>" section
in the Yocto Project Development Manual for more information about using <filename>devshell</filename>.
</para>
</section>
@ -532,6 +545,41 @@
</para>
</section>
<section id='ref-classes-distrodata'>
<title><filename>distrodata.bbclass</filename></title>
<para>
The Distribution Data (<filename>distrodata</filename>) class
provides for automatic checking for upstream recipe updates.
</para>
</section>
<section id='ref-classes-distutils'>
<title>Python Extensions - <filename>distutils.bbclass</filename></title>
<para>
Recipes for Python extensions are simple.
These recipes usually only need to point to the source's archive and then inherit
the proper <filename>.bbclass</filename> file.
Building is split into two methods depending on which method the module authors used.
<itemizedlist>
<listitem><para>Extensions that use an Autotools-based build system
require Autotools and
<filename>distutils</filename>-based classes in their recipes.
</para></listitem>
<listitem><para>Extensions that use
<filename>distutils</filename>-based build systems require
the <filename>distutils</filename> class in their recipes.
</para></listitem>
<listitem><para>Extensions that use the setuptools-based build
systems require the
<link linkend='ref-classes-setuptools'><filename>setuptools</filename></link>
class in their recipes.
</para></listitem>
</itemizedlist>
</para>
</section>
<section id='ref-classes-extrausers'>
<title><filename>extrausers.bbclass</filename></title>
@ -593,16 +641,6 @@
</para>
</section>
<section id='ref-classes-debian'>
<title>Debian Renaming - <filename>debian.bbclass</filename></title>
<para>
This class renames packages so that they follow the Debian naming
policy (i.e. <filename>eglibc</filename> becomes <filename>libc6</filename>
and <filename>eglibc-devel</filename> becomes <filename>libc6-dev</filename>.)
</para>
</section>
<section id='ref-classes-gconf'>
<title><filename>gconf.bbclass</filename></title>
@ -1666,44 +1704,6 @@
</para>
</section>
<section id='ref-classes-distutils'>
<title>Python Extensions - <filename>distutils.bbclass</filename></title>
<para>
Recipes for Python extensions are simple.
These recipes usually only need to point to the source's archive and then inherit
the proper <filename>.bbclass</filename> file.
Building is split into two methods depending on which method the module authors used.
<itemizedlist>
<listitem><para>Extensions that use an Autotools-based build system
require Autotools and
<filename>distutils</filename>-based classes in their recipes.
</para></listitem>
<listitem><para>Extensions that use
<filename>distutils</filename>-based build systems require
the <filename>distutils</filename> class in their recipes.
</para></listitem>
<listitem><para>Extensions that use the setuptools-based build
systems require the
<link linkend='ref-classes-setuptools'><filename>setuptools</filename></link>
class in their recipes.
</para></listitem>
</itemizedlist>
</para>
</section>
<section id='ref-classes-devshell'>
<title>Developer Shell - <filename>devshell.bbclass</filename></title>
<para>
This class adds the <filename>devshell</filename> task.
Distribution policy dictates whether to include this class.
See the
"<ulink url='&YOCTO_DOCS_DEV_URL;#platdev-appdev-devshell'>Using a Development Shell</ulink>" section
in the Yocto Project Development Manual for more information about using <filename>devshell</filename>.
</para>
</section>
<section id='ref-classes-packagegroup'>
<title>Package Groups - <filename>packagegroup.bbclass</filename></title>
@ -1725,7 +1725,6 @@
</para>
</section>
<section id='ref-classes-package'>
<title><filename>package.bbclass</filename></title>