mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-04-27 03:32:12 +02:00
Code Issues Packages Projects Releases Wiki Activity

sdk-manual: Edits to "Packaging" section.

Browse Source 
Edits to improve writing.

(From yocto-docs rev: 04d2df37ad718508c7f78a204d0d5e5fff431ce8)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-05-31 13:49:12 -07:00
committed by Richard Purdie
parent c0d1ff66ee
commit d527a5f7ab
1 changed files with 17 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
documentation/sdk-manual/sdk-extensible.xml
View File

@@ -1592,20 +1592,20 @@
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-package'><filename>do_package</filename></ulink>
task, files installed during the
<ulink url='&YOCTO_DOCS_REF_URL;#ref-tasks-install'><filename>do_install</filename></ulink>
task are split into one main package, which is almost always named
the same as the recipe, and several other packages.
This separation is done because not all of those installed files
are always useful in every image.
task are split into one main package, which is almost always
named the same as the recipe, and into several other packages.
This separation exists because not all of those installed files
are useful in every image.
For example, you probably do not need any of the documentation
installed in a production image.
Consequently, for each recipe the documentation files are separated
into a <filename>-doc</filename> package.
Recipes that package software that has optional modules or
plugins might do additional package splitting as well.
Consequently, for each recipe the documentation files are
separated into a <filename>-doc</filename> package.
Recipes that package software containing optional modules or
plugins might undergo additional package splitting as well.
</para>
<para>
After building a recipe you can see where files have gone by
After building a recipe, you can see where files have gone by
looking in the <filename>oe-workdir/packages-split</filename>
directory, which contains a subdirectory for each package.
Apart from some advanced cases, the
@@ -1615,17 +1615,18 @@
variables controls splitting.
The <filename>PACKAGES</filename> variable lists all of the
packages to be produced, while the <filename>FILES</filename>
variable specifies which files to include in each package,
variable specifies which files to include in each package by
using an override to specify the package.
For example, <filename>FILES_${PN}</filename> specifies the files
to go into the main package (i.e. the main package is named the
same as the recipe and
For example, <filename>FILES_${PN}</filename> specifies the
files to go into the main package (i.e. the main package has
the same name as the recipe and
<filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink><filename>}</filename>
evaluates to the recipe name).
The order of the <filename>PACKAGES</filename> value is significant.
The order of the <filename>PACKAGES</filename> value is
significant.
For each installed file, the first package whose
<filename>FILES</filename> value matches the file is the package
into which the file goes.
<filename>FILES</filename> value matches the file is the
package into which the file goes.
Defaults exist for both the <filename>PACKAGES</filename> and
<filename>FILES</filename> variables.
Consequently, you might find you do not even need to set these