Changeset 33325


Ignore:
Timestamp:
Jan 24, 2008, 6:18:34 AM (12 years ago)
Author:
markd@…
Message:

Refine wording in installation section.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc-new/guide/xml/installing.xml

    r33316 r33325  
    182182
    183183      <para>If you installed MacPorts using the package installer, skip this
    184       section. To install MacPorts from the source code, follow these
    185       steps.</para>
     184      section. To install MacPorts from the source code, follow the steps
     185      below.</para>
    186186
    187187      <orderedlist>
     
    193193
    194194        <listitem>
    195           <para>Perform these commands in a terminal window, substituting a
    196           real path for NEW_PREFIX if you wish to use a path other than
    197           <filename>/opt/local/</filename>.</para>
     195          <para>Perform the commands shown in a terminal window. If you wish
     196          to use a path other than <filename>/opt/local</filename>, use the
     197          option <option>--prefix</option> and substitute a path for
     198          NEW_PREFIX.</para>
    198199
    199200          <programlisting><prompt>%%</prompt> <userinput>cd ~/MacPorts-1.x.x/</userinput>
     
    208209
    209210        <para>Occasionally a MacPorts developer may wish to install more than
    210         one copy of MacPorts on the same host, possibly to test two different
    211         versions of MacPorts. But only one copy of MacPorts may use the
    212         default MacPorts Tcl library path <filename>/Library/Tcl/</filename>,
    213         so for a second installation use the
    214         <literal>--with-tclpackage</literal> switch set to any newly created
    215         (empty) directory, say /Library/Tcl/macports-new. Also, the standard
    216         MacPorts binary path must not be present during the installation of
    217         the second instance. To install a second instance of MacPorts, follow
    218         these steps.</para>
     211        one MacPorts instance on the same host. Only one copy of MacPorts may
     212        use the default Tcl library path <filename>/Library/Tcl/</filename>,
     213        so for additional installations use the option
     214        <option>--with-tclpackage</option> as shown below and substitute
     215        NEW_TCL_PACKAGE with any empty directory, for example
     216        <filename>/Library/Tcl/macports-new/</filename>.</para>
     217
     218        <note>
     219          <para>The first command temporarily removes the standard MacPorts
     220          binary paths because they must not be present while installing a
     221          second instance.</para>
     222        </note>
    219223
    220224        <programlisting><prompt>%%</prompt> <userinput>export PATH=/bin:/sbin:/usr/bin:/usr/sbin</userinput>
     
    246250    <para>MacPorts requires changes to the shell environment. If MacPorts was
    247251    installed using the Mac OS X package installer, a
    248     <quote>postflight</quote> script is run after the install that places a
    249     <filename>.profile</filename> file in your home directory populated with
    250     environmental variables set according to the detected Mac OS X version and
    251     environment.</para>
     252    <quote>postflight</quote> script was run after installation that places a
     253    <filename>.profile</filename> file in your home directory and populates it
     254    with environmental variables according to the detected Mac OS X version
     255    and environment. See details below.</para>
     256
     257    <note>
     258      <para>If a previous <filename>.profile</filename> is present it is
     259      renamed to "mpsaved_$timestamp" before the new .profile</para>
     260    </note>
    252261
    253262    <para>The <quote>postflight</quote> script sets environmental variables in
     
    264273
    265274      <listitem>
    266         <para>No MANPATH variable is set by <quote>postflight</quote> unless a
    267         MANPATH variable is already set in the current
    268         <filename>.profile</filename> file that does not include the value
    269         <filename>${prefix}/share/man,</filename> nor any empty values. In
    270         those cases, a MANPATH variable is added to
    271         <filename>.profile</filename> as shown.</para>
     275        <para>A MANPATH variable is set in <filename>.profile</filename> by
     276        the <quote>postflight</quote> script as shown only if a MANPATH
     277        variable was already set in a previous <filename>.profile</filename>
     278        that does not include the value
     279        <filename>${prefix}/share/man,</filename> nor any empty values.
     280        Otherwise it is omitted.</para>
    272281
    273282        <programlisting>export MANPATH=/opt/local/share/man:$MANPATH</programlisting>
     
    293302
    294303      <listitem>
    295         <para>No DISPLAY variable is set by <quote>postflight</quote> for Mac
    296         OS X 10.5 (Leopard) since it is not required to run X11 applications.
    297         However, for Mac OS X versions 10.4 and earlier the DISPLAY variable
    298         is required, so unless an existing DISPLAY variable was already set in
    299         a current <filename>.profile</filename>, the <quote>postflight</quote>
    300         script sets it as shown.</para>
     304        <para>A DISPLAY variable is set in <filename>.profile</filename> by
     305        the <quote>postflight</quote> script as shown only for X11 application
     306        support in Mac OS X versions 10.4 (Tiger) and earlier (unless DISPLAY
     307        is already set in a <filename>.profile</filename>). A DISPLAY variable
     308        is not set for Mac OS X 10.5 (Leopard) or higher.</para>
    301309
    302310        <programlisting>export DISPLAY=:0.0</programlisting>
Note: See TracChangeset for help on using the changeset viewer.