diff --git a/documentation/mega-manual/figures/analysis-for-package-splitting.png b/documentation/mega-manual/figures/analysis-for-package-splitting.png
index 5edf62c706..e312c84c4a 100644
Binary files a/documentation/mega-manual/figures/analysis-for-package-splitting.png and b/documentation/mega-manual/figures/analysis-for-package-splitting.png differ
diff --git a/documentation/ref-manual/figures/analysis-for-package-splitting.png b/documentation/ref-manual/figures/analysis-for-package-splitting.png
index 5edf62c706..e312c84c4a 100644
Binary files a/documentation/ref-manual/figures/analysis-for-package-splitting.png and b/documentation/ref-manual/figures/analysis-for-package-splitting.png differ
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 1b67ca7424..1171fec0a4 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -1130,38 +1130,49 @@
Package Splitting
- After source code configured and compiled, BitBake analyzes
- the results and splits the output into package:
+ After source code is configured and compiled, the
+ OpenEmbedded build system analyzes
+ the results and splits the output into packages:
The do_package and
do_packagedata tasks combine to analyze
- the data found in the
+ the files found in the
D directory
- and split it into subsets based on available packages and
+ and split them into subsets based on available packages and
files.
- The analyzing process involves splitting out debugging symbols,
- looking at shared library dependencies between packages, and
- looking at package relationships.
- The do_packagedata task puts package
- metadata based on the analysis such that BitBake can generate
- the final packages.
- Intermediate results of the package analysis and splitting
- end up in the
- PKGDEST
- directory with the
- FILES
- variable defining the files that go into the packages.
- If you want some details on how this is accomplished, you can
+ The analyzing process involves the following as well as other
+ items: splitting out debugging symbols,
+ looking at shared library dependencies between packages,
+ and looking at package relationships.
+ The do_packagedata task creates package
+ metadata based on the analysis such that the
+ OpenEmbedded build system can generate the final packages.
+ Working, staged, and intermediate results of the analysis
+ and package splitting process use these areas:
+
+ PKGD
+
+ PKGDATA_DIR
+
+ PKGDESTWORK
+
+ PKGDEST
+
+
+ The FILES
+ variable defines the files that go into each package in
+ PACKAGES.
+ If you want details on how this is accomplished, you can
look at
package.bbclass.
Depending on the type of packages being created (RPM, DEB, or
- IPK), the do_packagewrite_* task
+ IPK), the do_package_write_* task
creates the actual packages and places them in the
Package Feed area, which is
${TMPDIR}/deploy.
@@ -1173,9 +1184,10 @@
deploy/* directories does not exist.
Creating such feeds usually requires some kind of feed
maintenance mechanism that would upload the new packages
- into an official package feed (e.g. angstrom).
- Providing such a piece for the user is not feasible since
- it is very distribution-specific.
+ into an official package feed (e.g. the
+ Ångström distribution).
+ This functionality is highly distribution-specific
+ and thus is not provided out of the box.