sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation: poky-ref-manual - edits to build history section. 

Applied some review comments from Paul Eggleton on the new
build history section.  Some minor re-phrasing.

(From yocto-docs rev: 986b0e7d2a79141d7c8dea0062cd25970a74fa57)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2012-11-15 15:17:31 -08:00 committed by Richard Purdie
parent decd7785ad
commit fa30b8b563
1 changed files with 13 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
documentation/poky-ref-manual/usingpoky.xml
View File

@ -364,7 +364,7 @@
<title>Maintaining Build Output Quality</title>
<para>
A build's quality can be influenced by several things.
A build's quality can be influenced by many things.
For example, if you upgrade a recipe to use a new version of an upstream software
package or you experiment with some new configuration options, subtle changes
can occur that you might not detect until later.
@ -413,7 +413,8 @@
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
</literallayout>
Enabling build history causes the build process to collect build
Enabling build history as previously described
causes the build process to collect build
output information and commit it to a local
<ulink url='&YOCTO_DOCS_DEV_URL;#git'>Git</ulink> repository.
<note>
@ -430,7 +431,9 @@
build history in this manner can change the
<filename>do_package</filename> task checksums, which if you
are using the OEBasicHash signature generator (the default
for some distro configurations) will result in the packaging
for many current distro configurations including
<filename>DISTRO = "poky"</filename> and
<filename>DISRTO = ""</filename>) will result in the packaging
tasks being re-run during the subsequent build.
</para>
@ -531,8 +534,9 @@
filenames.</para></listitem>
</itemizedlist>
<note>
Installed package information is able to be gathered and
produced even if packaging is disabled for the final image.
Installed package information is able to be gathered and
produced even if package management is disabled for the final
image.
</note>
</para>
@ -561,8 +565,8 @@
</para>
</section>
<section id='limiting-build-history-information'>
<title>Limiting Build History Information</title>
<section id='using-build-history-to-gather-image-information-only'>
<title>Using Build History to Gather Image Information Only</title>
<para>
As you can see, build history produces image information,
@ -570,7 +574,8 @@
was pulled into the image.
If you are just interested in this information and not
interested in collecting history or any package information,
you can limit the build history output by adding the following
you can enable writing only image information without
any history by adding the following
to your <filename>conf/local.conf</filename> file found in the
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
<literallayout class='monospaced'>