Changeset 33346dd for BOOK/final-system


Ignore:
Timestamp:
May 20, 2014, 9:36:31 PM (10 years ago)
Author:
Chris Staub <chris@…>
Branches:
clfs-3.0.0-sysvinit, sysvinit
Children:
9a65833
Parents:
1de8183
git-author:
Chris Staub <chris@…> (05/20/14 02:30:28)
git-committer:
Chris Staub <chris@…> (05/20/14 21:36:31)
Message:

More consistently use 'test suite' rather than 'testsuite'

Conflicts:

BOOK/appendices/dependencies/common.xml
BOOK/final-system/common/dbus.xml

Location:
BOOK/final-system/common
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • BOOK/final-system/common/coreutils.xml

    r1de8183 r33346dd  
    6262<screen os="h"><userinput remap="test">make NON_ROOT_USERNAME=nobody check-root</userinput></screen>
    6363
    64     <para os="i">The testsuite will now be run as the
     64    <para os="i">The test suite will now be run as the
    6565    <systemitem class="username">nobody</systemitem> user. Some tests require
    6666    that the user be a member of more than one group. Add a temporary group

  • BOOK/final-system/common/glibc.xml

    r1de8183 r33346dd  
    103103    </important>
    104104
    105     <para os="m">Use the following commands to run the testsuite and output
     105    <para os="m">Use the following commands to run the test suite and output
    106106    any test failures:</para>
    107107

  • BOOK/final-system/common/perl.xml

    r1de8183 r33346dd  
    4444    <para os="a01">Before starting to configure, create a basic
    4545    <filename>/etc/hosts</filename> file which will be referenced by one
    46     of Perl's configuration files as well as used by the testsuite:</para>
     46    of Perl's configuration files as well as used by the test suite:</para>
    4747
    4848<screen os="a02"><userinput remap="test">echo "127.0.0.1 localhost $(hostname)" &gt; /etc/hosts</userinput></screen>

  • BOOK/final-system/common/testsuitesagain.xml

    r1de8183 r33346dd  
    1212
    1313  <para>In the final-system build, you are no longer cross-compiling so it
    14   is possible to run package testsuites. Running the test suite for a
     14  is possible to run package test suites. Running the test suite for a
    1515  newly built package is a good idea because it can provide a <quote>sanity
    1616  check</quote> indicating that everything compiled correctly. A test suite
Note: See TracChangeset for help on using the changeset viewer.