First stage towards Bug 719. Making the Chapter 5 test suites

strictly optional.


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3170 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter02/abouttestsuites.xml

@@ -16,6 +16,15 @@ properly functioning system. But be warned, the test suites for GCC and Glibc
 can take a very long period of time to complete, especially on slower
 hardware.</para>
 
+<para>Experience has shown us that there is little to be gained from running
+the test suites in Chapter 5. There can be no escaping the fact that the host
+system always exerts influence on the Chapter 5 tests, often causing weird and
+inexplicable failures. Not only that, the tools built in Chapter 5 are
+temporary and eventually discarded. For the average reader of this book we
+recommend not to run the Chapter 5 test suites. The instructions for running
+the Chapter 5 test suites are still provided for the benefit of testers and
+developers but they are strictly optional for everyone else.</para>
+
 <para>As you progress through the book and encounter the build commands to
 run the various test suites, we'll guide you on the relative importance of
 the test suite in question so that you can decide for yourself whether to

chapter05/bash.xml

@@ -26,9 +26,9 @@ patch:</para>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly.  Should you choose to run it, the 
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Bash test
+suite anyway, the following command will do so:</para>
 
 <screen><userinput>make tests</userinput></screen>
 

chapter05/coreutils.xml

@@ -23,9 +23,9 @@ Estimated required disk space:  &coreutils-compsize-tools;</screen>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly.  Should you choose to run it, the 
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Coreutils
+test suite anyway, the following command will do so:</para>
 
 <screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen>
 

chapter05/expect.xml

@@ -44,12 +44,12 @@ libraries, both of which may possibly reside on the host system.</para></listite
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly. However, the Expect test suite
-is known to experience failures under certain host conditions that
-are not fully understood. Therefore, test suite failures here are not
-surprising, and are not considered critical. Should you choose to run the test
-suite, the following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Expect test
+suite anyway, the following command will do so. However, you should be aware
+that the Expect test suite is sometimes known to experience failures under
+certain host conditions that are not fully understood. Therefore, test suite
+failures here are not surprising, but are not considered critical:</para>
 
 <screen><userinput>make test</userinput></screen>
 

chapter05/findutils.xml

@@ -21,9 +21,9 @@ Estimated required disk space:  &findutils-compsize-tools;</screen>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly.  Should you choose to run it, the 
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Findutils
+test suite anyway, the following command will do so:</para>
 
 <screen><userinput>make check</userinput></screen>
 

chapter05/gawk.xml

@@ -23,9 +23,9 @@ Estimated required disk space:  &gawk-compsize-tools;</screen>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly. Should you choose to run it, the
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Gawk test
+suite anyway, the following command will do so:</para>
 
 <screen><userinput>make check</userinput></screen>
 

chapter05/gettext.xml

@@ -21,14 +21,14 @@ Estimated required disk space:  &gettext-compsize-tools;</screen>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly. However, the Gettext test suite is known
-to experience failures under certain host conditions -- for
-example, if it finds a Java compiler on the host (Note: an experimental patch
-to disable Java is available from the patches project). The Gettext test suite
-takes a very long time to run and is not considered critical. Therefore,
-we don't recommend running it here. Should you choose to run it, the following
-command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Gettext test
+suite anyway, the following command will do so. However, you should be aware
+that the Gettext test suite is known to experience failures under certain host
+conditions -- for example, when it finds a Java compiler on the host (Note: an
+experimental patch to disable Java is available from the patches project). Not
+only that, the Gettext test suite takes an excessive amount of time to run and
+is not considered critical:</para>
 
 <screen><userinput>make check</userinput></screen>
 

chapter05/grep.xml

@@ -34,9 +34,9 @@ the code from Glibc, which is known to be slightly buggy.</para></listitem>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly.  Should you choose to run it, the 
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Grep test
+suite anyway, the following command will do so:</para>
 
 <screen><userinput>make check</userinput></screen>
 

chapter05/make.xml

@@ -21,9 +21,9 @@ Estimated required disk space:  &make-compsize-tools;</screen>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly.  Should you choose to run it, the 
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Make test
+suite anyway, the following command will do so:</para>
 
 <screen><userinput>make check</userinput></screen>
 

chapter05/sed.xml

@@ -21,9 +21,9 @@ Estimated required disk space:  &sed-compsize-tools;</screen>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly.  Should you choose to run it, the 
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Sed test
+suite anyway, the following command will do so:</para>
 
 <screen><userinput>make check</userinput></screen>
 

chapter05/tar.xml

@@ -21,9 +21,9 @@ Estimated required disk space:  &tar-compsize-tools;</screen>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly.  Should you choose to run it, the 
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Tar test
+suite anyway, the following command will do so:</para>
 
 <screen><userinput>make check</userinput></screen>
 

chapter05/tcl.xml

@@ -29,12 +29,12 @@ to know that our most important tools are working properly.</para>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly. However, the Tcl test suite in this
-chapter is known to experience failures under certain host conditions that are
-not fully understood. Therefore, test suite failures here are not surprising,
-but are not considered critical. Should you choose to run the test suite, the
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Tcl test
+suite anyway, the following command will do so. However, you should be aware
+that the Tcl test suite is sometimes known to experience failures under certain
+host conditions that are not fully understood. Therefore, test suite failures
+here are not surprising, but are not considered critical:</para>
 
 <screen><userinput>TZ=UTC make test</userinput></screen>
 

chapter05/texinfo.xml

@@ -21,9 +21,9 @@ Estimated required disk space:  &texinfo-compsize-tools;</screen>
 
 <screen><userinput>make</userinput></screen>
 
-<para>This package has a test suite available which can perform a number of
-checks to ensure it built correctly.  Should you choose to run it, the 
-following command will do so:</para>
+<para>As discussed earlier, we don't recommend running the test suites for the
+temporary tools here in this chapter. If you still want to run the Texinfo test
+suite anyway, the following command will do so:</para>
 
 <screen><userinput>make check</userinput></screen>
 

index.xml

@@ -2,8 +2,8 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
 			"/usr/share/docbook/docbookx.dtd" [
 
-<!ENTITY version "CVS-2004-01-14">
-<!ENTITY releasedate "January 14th, 2004">
+<!ENTITY version "CVS-2004-01-16">
+<!ENTITY releasedate "January 16th, 2004">
 <!ENTITY milestone "5.1">
 <!ENTITY nbsp " ">