diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 0d3d59355c..7a5a375c0e 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -917,23 +917,29 @@
Customizing Images Using Custom Package Groups
- 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
meta/recipes-core/packagegroups/packagegroup-core-boot.bb.
The
PACKAGES
- variable lists the package group packages you wish to produce. inherit packagegroup
- sets appropriate default values and automatically adds -dev
- and -dbg complementary
- packages for every package specified in 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.
- For each package you specify in PACKAGES, you can use
+ the top of the recipe, certainly before you set
+ PACKAGES.
+ For each package you specify in PACKAGES,
+ you can use
RDEPENDS
and
RRECOMMENDS
- 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:
DESCRIPTION = "My Custom Package Groups"