Ignore:
Timestamp:
02/03/2019 06:37:53 PM (5 years ago)
Author:
DJ Lucas <dj@…>
Branches:
elogind
Children:
4d176c4f
Parents:
8f6f10e
Message:

Merge to HEAD 21080.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/branches/BOOK-elogind@21081 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed

  • general/prog/scour.xml

    r8f6f10e rd60cd837  
    6969      <bridgehead renderas="sect4">Scour Dependencies</bridgehead>
    7070
    71       <!-- Required: only setuptools, which is available from our Python and
    72       Python3 installs via pypi (it has a recursive dependency) -->
     71      <bridgehead renderas="sect5">Required</bridgehead>
     72      <para role="required">
     73        <xref linkend="six"/> (will be automatically downloaded and installed
     74        if not already present)
     75      </para>
    7376
    7477      <bridgehead renderas="sect5">Recommended</bridgehead>
    … …  
    8487      </note>
    8588
    86       <bridgehead renderas="sect5">Optional (for the main test)</bridgehead>
    87       <para role="optional">
    88         <xref linkend="six"/>
    89       </para>
    90 
    9189      <para condition="html" role="usernotes">
    9290        User Notes: <ulink url="&blfs-wiki;/scour"/>
    … …  
    9795      <title>Installation of scour</title>
    9896
     97
    9998      <note>
    10099        <para>
    101           Although this package installs modules for <application>Python
    102           2</application> <emphasis>or</emphasis> <application>Python
    103           3</application> they are usually invoked by <command>scour</command>
    104           which is a script using the version of
    105           <application>Python</application> for which it was compiled.
    106         </para>
    107 
    108         <para>
    109           For the moment, use of <application>Python 2</application> will
    110           normally be adequate.
     100          Both <application>Python 2</application> and
     101          <application>Python 3</application> modules can
     102          be built and installed without any conflicts.
    111103        </para>
    112104      </note>
    113105
    114 <!-- Editors note: Use \-\-root= instead of DESTDIR= when updating. -->
     106<!-- Editors note: Use - -root= instead of DESTDIR= when updating. -->
    115107
    116108      <para>
    117         To build the <application>Python 2</application> module, issue:
     109        To build the <application>Python 2</application> module,
     110        run the following command:
    118111      </para>
    119112
    … …  
    134127<screen role="root"><userinput>python setup.py install --optimize=1</userinput></screen>
    135128
    136       <note>
    137         <para>
    138           If you wish to install the <application>Python 3</application>
    139           modules, change 'python' to 'python3' in each of the above steps.
    140         </para>
    141       </note>
     129      <para>
     130        To build the <application>Python 3</application> module,
     131        run the following command:
     132      </para>
     133
     134<screen><userinput>python3 setup.py build</userinput></screen>
     135
     136      <para>
     137        To install the <application>Python 3</application> module,
     138        run the following command as the
     139        <systemitem class="username">root</systemitem> user:
     140      </para>
     141
     142<screen role="root"><userinput>python3 setup.py install --optimize=1</userinput></screen>
    142143
    143144    </sect3>
Note: See TracChangeset for help on using the changeset viewer.