From a8aa6bd6790098d780f596daefdc432ee68ba3fc Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 10 Dec 2013 11:27:27 -0600 Subject: [PATCH] ref-manual: Updated the PACKAGE_CLASSES variable description. This was pathetic and needed updating. (From yocto-docs rev: 6dd88094a07da56efc752dea0b447f65b25d276a) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 46 ++++++++++++++++++---- 1 file changed, 38 insertions(+), 8 deletions(-) diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index d4072f1b8d..262fd0b39a 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -4340,17 +4340,47 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" PACKAGE_CLASSES - This variable, which is set in the local.conf configuration - file found in the conf folder of the + + This variable, which is set in the + local.conf configuration file found in + the conf folder of the Build Directory, - specifies the package manager to use when packaging data. - You can provide one or more arguments for the variable with the first - argument being the package manager used to create images: + specifies the package manager the OpenEmbedded build system + uses when packaging data. + + + + You can provide one or more of the following arguments for + the variable: - PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" + PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk package_tar" - For information on build performance effects as a result of the - package manager use, see the + The build system uses only the first argument in the list + as the package manager when creating your image or SDK. + However, packages will be created using any additional + packaging classes you specify. + For example, if you use the following in your + local.conf file: + + PACKAGE_CLASSES ?= "package_ipk package_tar" + + The OpenEmbedded build system uses the IPK package manager + to create your image or SDK as well as generating + TAR packages. + + + + You cannot specify the + package_tar + class first in the list. + Files using the .tar format cannot + be used as a substitute packaging format + for DEB, RPM, and IPK formatted files for you image or SDK. + + + + For information on packaging and build performance effects + as a result of the package manager in use, see the "package.bbclass" section.