dev-manual: updated the ptest section

Removed the note indicating that three specific recipes were
"ptest-enabled" for the release.  I substituted in wording that
tells the user to see if a a recipe inherits ptest as a way
of determining if the receipe is ptest-enabled.

(From yocto-docs rev: f9886957055619e9c5e9eccfe0a606e7aee275cd)

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-11-18 06:45:42 -08:00 committed by Richard Purdie
parent 2c5640cdb4
commit 2c45a8c3ff
1 changed files with 2 additions and 6 deletions

View File

@ -902,7 +902,7 @@
</para> </para>
<para> <para>
Defining the software using a custom recipe gives you total Defining the software using a custom recipe gives you total
control over the contents of the image. control over the contents of the image.
It is important to use the correct names of packages in the It is important to use the correct names of packages in the
<filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'>IMAGE_INSTALL</ulink></filename> <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'>IMAGE_INSTALL</ulink></filename>
@ -4789,11 +4789,7 @@ the details.
</para> </para>
<note> <note>
With this release of the Yocto Project, three recipes exist A recipe is "ptest-enabled" if it inherits ptest.
that are "ptest-enabled": <filename>bash</filename>,
<filename>glib-2.0</filename>, and
<filename>dbus</filename>.
These three recipes are Autotool-enabled.
</note> </note>
<section id='adding-ptest-to-your-build'> <section id='adding-ptest-to-your-build'>