From 17ac9ee19475b2d67bd825479f683461829748bc Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 18 Nov 2013 06:45:42 -0800 Subject: 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 Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-common-tasks.xml | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) (limited to 'documentation') 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 @@ - 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 IMAGE_INSTALL @@ -4058,11 +4058,7 @@ - With this release of the Yocto Project, three recipes exist - that are "ptest-enabled": bash, - glib-2.0, and - dbus. - These three recipes are Autotool-enabled. + A recipe is "ptest-enabled" if it inherits ptest.
-- cgit v1.2.3-54-g00ecf