summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-11-15 15:17:31 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-12-03 13:52:56 +0000
commitfa30b8b56353adb8f295bcd3926d8d6a7ff45e96 (patch)
treedec7f6f357335ffd4f3cf16a03728b559167948f
parentdecd7785ad984271d41176ebe0a6f573a392578d (diff)
downloadpoky-fa30b8b56353adb8f295bcd3926d8d6a7ff45e96.tar.gz
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>
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml21
1 files changed, 13 insertions, 8 deletions
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index 567e721e4e..82d2312994 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -364,7 +364,7 @@
364 <title>Maintaining Build Output Quality</title> 364 <title>Maintaining Build Output Quality</title>
365 365
366 <para> 366 <para>
367 A build's quality can be influenced by several things. 367 A build's quality can be influenced by many things.
368 For example, if you upgrade a recipe to use a new version of an upstream software 368 For example, if you upgrade a recipe to use a new version of an upstream software
369 package or you experiment with some new configuration options, subtle changes 369 package or you experiment with some new configuration options, subtle changes
370 can occur that you might not detect until later. 370 can occur that you might not detect until later.
@@ -413,7 +413,8 @@
413 INHERIT += "buildhistory" 413 INHERIT += "buildhistory"
414 BUILDHISTORY_COMMIT = "1" 414 BUILDHISTORY_COMMIT = "1"
415 </literallayout> 415 </literallayout>
416 Enabling build history causes the build process to collect build 416 Enabling build history as previously described
417 causes the build process to collect build
417 output information and commit it to a local 418 output information and commit it to a local
418 <ulink url='&YOCTO_DOCS_DEV_URL;#git'>Git</ulink> repository. 419 <ulink url='&YOCTO_DOCS_DEV_URL;#git'>Git</ulink> repository.
419 <note> 420 <note>
@@ -430,7 +431,9 @@
430 build history in this manner can change the 431 build history in this manner can change the
431 <filename>do_package</filename> task checksums, which if you 432 <filename>do_package</filename> task checksums, which if you
432 are using the OEBasicHash signature generator (the default 433 are using the OEBasicHash signature generator (the default
433 for some distro configurations) will result in the packaging 434 for many current distro configurations including
435 <filename>DISTRO = "poky"</filename> and
436 <filename>DISRTO = ""</filename>) will result in the packaging
434 tasks being re-run during the subsequent build. 437 tasks being re-run during the subsequent build.
435 </para> 438 </para>
436 439
@@ -531,8 +534,9 @@
531 filenames.</para></listitem> 534 filenames.</para></listitem>
532 </itemizedlist> 535 </itemizedlist>
533 <note> 536 <note>
534 Installed package information is able to be gathered and 537 Installed package information is able to be gathered and
535 produced even if packaging is disabled for the final image. 538 produced even if package management is disabled for the final
539 image.
536 </note> 540 </note>
537 </para> 541 </para>
538 542
@@ -561,8 +565,8 @@
561 </para> 565 </para>
562 </section> 566 </section>
563 567
564 <section id='limiting-build-history-information'> 568 <section id='using-build-history-to-gather-image-information-only'>
565 <title>Limiting Build History Information</title> 569 <title>Using Build History to Gather Image Information Only</title>
566 570
567 <para> 571 <para>
568 As you can see, build history produces image information, 572 As you can see, build history produces image information,
@@ -570,7 +574,8 @@
570 was pulled into the image. 574 was pulled into the image.
571 If you are just interested in this information and not 575 If you are just interested in this information and not
572 interested in collecting history or any package information, 576 interested in collecting history or any package information,
573 you can limit the build history output by adding the following 577 you can enable writing only image information without
578 any history by adding the following
574 to your <filename>conf/local.conf</filename> file found in the 579 to your <filename>conf/local.conf</filename> file found in the
575 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>: 580 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
576 <literallayout class='monospaced'> 581 <literallayout class='monospaced'>