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: 9136617575eb7a0a08f0b81f75ae6cdede62219f)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 2 insertions, 6 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 8ef3d2e0fd..7138f5dca6 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -902,7 +902,7 @@
             </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.
                 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>
@@ -4058,11 +4058,7 @@
             </para>
 
             <note>
-                With this release of the Yocto Project, three recipes exist
-                that are "ptest-enabled": <filename>bash</filename>,
-                <filename>glib-2.0</filename>, and
-                <filename>dbus</filename>.
-                These three recipes are Autotool-enabled.
+                A recipe is "ptest-enabled" if it inherits ptest.
             </note>
 
             <section id='adding-ptest-to-your-build'>