diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index a690544364..5a7d111890 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -601,6 +601,58 @@
+
+ Package Feeds
+
+
+ When the OpenEmbedded build system generates an image or an SDK,
+ it gets the packages from a package feed area located in the
+ Build Directory.
+ The
+ general Yocto Project Development Environment figure
+ shows this package feeds area in the upper-right corner.
+
+
+
+ This section looks a little closer into the package feeds area used
+ by the build system.
+ Here is a more detailed look at the area:
+
+
+
+
+ Package feeds are an intermediary step in the build process.
+ BitBake generates packages whose type is defined by the
+ PACKAGE_CLASSES
+ variable.
+ Before placing the packages into package feeds,
+ the build process validates them with generated output quality
+ assurance checks through the
+ insane.bbclass
+ class.
+
+
+
+ The package feed area resides in
+ tmp/deploy of the Build Directory.
+ Folders are created that correspond to the package type
+ (IPK, DEB, or RPM) created.
+ Further organization is derived through the value of the
+ PACKAGE_ARCH
+ variable for each package.
+ For example, packages can exist for the i586 or qemux86
+ architectures.
+ The package files themselves reside within the appropriate
+ architecture folder.
+
+
+
+ BitBake uses the do_package_write_* task to
+ place generated packages into the package holding area (e.g.
+ do_package_write_ipk for IPK packages).
+
+
+
BitBake
@@ -844,12 +896,15 @@
The image generation process consists of several stages and
depends on many variables.
- The do_rootfs uses these key variables
+ The do_rootfs task uses these key variables
to help create the list of packages to actually install:
IMAGE_INSTALL:
Lists out the base set of packages to install from
the Package Feeds area.
+ PACKAGE_EXCLUDE:
+ Specifies packages that should not be installed.
+ IMAGE_FEATURES:
Specifies features to include in the image.
These features map to additional packages for
@@ -858,20 +913,12 @@
Specifies the package manager to use and consequently
helps determine where to locate packages within the
Package Feeds area.
- PACKAGE_EXCLUDE:
- Specifies packages that should not be installed.
-
+ IMAGE_LINGUAS:
+ Determines the language for which packages are being
+ installed.
-
- In addition to the previously mentioned variables, the image
- generation process uses
- IMAGE_LINGUAS
- to determine what language for which packages are being
- installed.
-
-
Part of the image generation process includes compressing the
root filesystem image.
@@ -923,58 +970,6 @@
-
- Package Feeds
-
-
- When the OpenEmbedded build system generates an image or an SDK,
- it gets the packages from a package feed area located in the
- Build Directory.
- The
- general Yocto Project Development Environment figure
- shows this package feeds area in the upper-right corner.
-
-
-
- This section looks a little closer into the package feeds area used
- by the build system.
- Here is a more detailed look at the area:
-
-
-
-
- Package feeds are an intermediary step in the build process.
- BitBake generates packages whose type is defined by the
- PACKAGE_CLASSES
- variable.
- Before placing the packages into package feeds,
- the build process validates them with generated output quality
- assurance checks through the
- insane.bbclass
- class.
-
-
-
- The package feed area resides in
- tmp/deploy of the Build Directory.
- Folders are created that correspond to the package type
- (IPK, DEB, or RPM) created.
- Further organization is derived through the value of the
- PACKAGE_ARCH
- variable for each package.
- For example, packages can exist for the i586 or qemux86
- architectures.
- The package files themselves reside within the appropriate
- architecture folder.
-
-
-
- BitBake uses the do_package_write_* task to
- place generated packages into the package holding area (e.g.
- do_package_write_ipk for IPK packages).
-
-
-
Images