From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Tue, 22 Oct 2013 15:58:21 +0000 (-0700)
Subject: dev-manual: Added -ptest to list of complementarty packages
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fe0292764a1c536504695b9a23ef18f3a0376777;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git

dev-manual: Added -ptest to list of complementarty packages

Added the '-ptest' complementary package to the list of packages,
which included '-dev' and '-dbg' when using inherit packagegroup.
Robert P. J. Day pointed out the code in the OE packagegroup.bbclass
class that showed these three packages all together.

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 823555ac44958995426cc631d992b9d276c42ca4)

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

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 0d3d59355c7..7a5a375c0e7 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -917,23 +917,29 @@
             <title>Customizing Images Using Custom Package Groups</title>
 
             <para>
-                For complex custom images, the best approach is to create a custom package group recipe
-                that is used to build the image or images.
+                For complex custom images, the best approach is to create a
+                custom package group recipe that is used to build the image or
+                images.
                 A good example of a package group recipe is
                 <filename>meta/recipes-core/packagegroups/packagegroup-core-boot.bb</filename>.
                 The
                 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGES'>PACKAGES</ulink></filename>
-                variable lists the package group packages you wish to produce. <filename>inherit packagegroup</filename>
-                sets appropriate default values and automatically adds <filename>-dev</filename>
-                and <filename>-dbg</filename> complementary
-                packages for every package specified in <filename>PACKAGES</filename>.
+                variable lists the package group packages you wish to produce.
+                <filename>inherit packagegroup</filename> sets appropriate
+                default values and automatically adds <filename>-dev</filename>,
+                <filename>-dbg</filename>, and <filename>-ptest</filename>
+                complementary packages for every package specified in
+                <filename>PACKAGES</filename>.
                 Note that the inherit line should be towards
-                the top of the recipe, certainly before you set <filename>PACKAGES</filename>.
-                For each package you specify in <filename>PACKAGES</filename>, you can use
+                the top of the recipe, certainly before you set
+                <filename>PACKAGES</filename>.
+                For each package you specify in <filename>PACKAGES</filename>,
+                you can use
                 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-RDEPENDS'>RDEPENDS</ulink></filename>
                 and
                 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-RRECOMMENDS'>RRECOMMENDS</ulink></filename>
-                entries to provide a list of packages the parent task package should contain.
+                entries to provide a list of packages the parent task package
+                should contain.
                 Following is an example:
                 <literallayout class='monospaced'>
      DESCRIPTION = "My Custom Package Groups"