diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 9503593f61..17d725b3b8 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1100,18 +1100,27 @@
an image 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
- meta/recipes-core/packagegroups/packagegroup-core-boot.bb.
- The
+ meta/recipes-core/packagegroups/packagegroup-base.bb.
+
+
+
+ If you examine that recipe, you see that the
PACKAGES
- variable lists the package group packages you wish to produce.
- inherit packagegroup sets appropriate
- default values and automatically adds -dev,
- -dbg, and -ptest
- complementary packages for every package specified in
- PACKAGES.
- Note that the inherit line should be towards
- the top of the recipe, certainly before you set
- PACKAGES.
+ variable lists the package group packages to produce.
+ The inherit packagegroup statement
+ sets appropriate default values and automatically adds
+ -dev, -dbg, and
+ -ptest complementary packages for each
+ package specified in the PACKAGES
+ statement.
+
+ The inherit packages should be
+ located near the top of the recipe, certainly before
+ the PACKAGES statement.
+
+
+
+
For each package you specify in PACKAGES,
you can use
RDEPENDS
@@ -1119,7 +1128,13 @@
RRECOMMENDS
entries to provide a list of packages the parent task package
should contain.
- Following is an example:
+ You can see examples of these further down in the
+ packagegroup-base.bb recipe.
+
+
+
+ Here is a short, fabricated example showing the same basic
+ pieces:
DESCRIPTION = "My Custom Package Groups"