[Clfs-commits] [Cross-LFS]Cross-LFS Book branch, sysvinit, updated. clfs-2.1.0-1056-g5f63ccf

[git]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Cross-LFS Book".

The branch, sysvinit has been updated
       via  5f63ccf34162a207775a8b6be154a75c07019ed0 (commit)
      from  dbf50c0cb8fc273a0ab0aa4a7f397f2e065d23e7 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 5f63ccf34162a207775a8b6be154a75c07019ed0
Author: Chris Staub <chris at beaker67.com>
Date:   Sun May 18 00:50:17 2014 -0400

    Reworded test suite pages

diff --git a/BOOK/final-preps/abouttestsuites.xml b/BOOK/final-preps/abouttestsuites.xml
index 513c99d..a597a44 100644
--- a/BOOK/final-preps/abouttestsuites.xml
+++ b/BOOK/final-preps/abouttestsuites.xml
@@ -10,13 +10,11 @@
 
   <title>About the Test Suites</title>
 
-  <para>Most packages provide a test suite. Running the test suite for a
-  newly built package is a good idea because it can provide a <quote>sanity
-  check</quote> indicating that everything compiled correctly. A test suite
-  that passes its set of checks usually proves that the package is
-  functioning as the developer intended. It does not, however, guarantee
-  that the package is totally bug free.</para>
-
-  <para>It is not possible to run testsuites when cross-compiling, so package installation instructions do not explain how to run testsuites until <xref linkend="chapter-building-system"/>.</para>
+  <para>Most packages provide a test suite, usually a script or
+  <command>make</command> target, which tests the just-compiled programs or
+  libraries by executing or linking to them. Test suites are often useful
+  for verifying that a package compiled correctly. However, they cannot
+  be run while cross-compiling so we will not mention test suite commands
+  for any packages until <xref linkend="chapter-building-system"/>.</para>
 
 </sect1>
diff --git a/BOOK/final-system/common/testsuitesagain.xml b/BOOK/final-system/common/testsuitesagain.xml
index 9281a49..64c20a9 100644
--- a/BOOK/final-system/common/testsuitesagain.xml
+++ b/BOOK/final-system/common/testsuitesagain.xml
@@ -11,9 +11,16 @@
   <title>About Test Suites, Again</title>
 
   <para>In the final-system build, you are no longer cross-compiling so it
-  is possible to run package testsuites. Some test suites are more important
-  than others. For example,  the test suites for the core toolchain
-  packages—GCC, Binutils, and Glibc—are of the utmost
+  is possible to run package testsuites. Running the test suite for a
+  newly built package is a good idea because it can provide a <quote>sanity
+  check</quote> indicating that everything compiled correctly. A test suite
+  that passes its set of checks usually proves that the package is
+  functioning as the developer intended. It does not, however, guarantee
+  that the package is totally bug free.</para>
+
+  <para>Some test suites are more important than others. For example, the test
+  suites for the core toolchain packages—GCC, Binutils,
+  and Glibc—are of the utmost
   importance due to their central role in a properly functioning system.
   The test suites for GCC and Glibc can take a very long time to complete,
   especially on slower hardware, but are strongly recommended.</para>

-----------------------------------------------------------------------

Summary of changes:
 BOOK/final-preps/abouttestsuites.xml         |   14 ++++++--------
 BOOK/final-system/common/testsuitesagain.xml |   13 ++++++++++---
 2 files changed, 16 insertions(+), 11 deletions(-)


hooks/post-receive
-- 
Cross-LFS Book