Changeset 33354


Ignore:
Timestamp:
Jan 24, 2008, 9:16:57 PM (12 years ago)
Author:
markd@…
Message:

Refinements and corrections.

File:
1 edited

Legend:

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

    r33325 r33354  
    138138    <filename>/opt/local/</filename>, the default MacPorts location, or if you
    139139    wish to install a pre-release version of MacPorts base. However, if you
    140     wish to install <ulink url="installing.source.multiple">multiple copies of
    141     MacPorts</ulink> or install MacPorts on another OS platform, you must
     140    wish to <link linkend="installing.source.multiple">install multiple copies
     141    of MacPorts</link> or install MacPorts on another OS platform, you must
    142142    <link linkend="installing.source">install MacPorts from the source
    143143    code</link>.</para>
     
    251251    installed using the Mac OS X package installer, a
    252252    <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>
    261 
    262     <para>The <quote>postflight</quote> script sets environmental variables in
    263     the <filename>.profile</filename> file as shown.</para>
     253    <filename>.profile</filename> file in the home directory, which
     254    automatically contains the environmental variables required for MacPorts.
     255    If a current <filename>.profile</filename> file exists at installation
     256    time it is renamed to "mpsaved_$timestamp".</para>
     257
     258    <note>
     259      <para>If you have either a <filename>.bash_login</filename> or a
     260      <filename>.bash_profile</filename> file in your home directory, they may
     261      take precedence over <filename>.profile</filename>. You may either
     262      remove the previously used file, or add the contents of
     263      <filename>.profile</filename> to it.</para>
     264    </note>
     265
     266    <para>The postflight script automatically copies a
     267    <filename>.profile</filename> containing variables according to the rules
     268    described below. Those <link linkend="installing.source">installing
     269    MacPorts from source code</link> must modify their environment manually
     270    using the rules below as a guide. </para>
     271
     272    <note>
     273      <para>Be sure to notice in the rules below that the variables MANPATH
     274      and DISPLAY are only set under certain conditions.</para>
     275    </note>
    264276
    265277    <itemizedlist>
    266278      <listitem>
    267         <para>A PATH variable is set to append the MacPorts file paths in
    268         front of the default file paths so MacPorts libraries will take
    269         precedence over vendor-supplied libraries.</para>
     279        <para>A PATH variable is set as shown regardless of platform or
     280        environment that appends the MacPorts file paths in front of the
     281        default file paths so MacPorts libraries will take precedence over
     282        vendor-supplied libraries.</para>
    270283
    271284        <programlisting>export PATH=/opt/local/bin:/opt/local/sbin:$PATH</programlisting>
     
    273286
    274287      <listitem>
    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>
     288        <para>A MANPATH variable is set as shown only if a MANPATH variable
     289        was already set in a previous <filename>.profile</filename> that does
     290        not include the value <filename>${prefix}/share/man,</filename> nor
     291        any empty values. Otherwise it is omitted.</para>
    281292
    282293        <programlisting>export MANPATH=/opt/local/share/man:$MANPATH</programlisting>
    283294
    284         <note>
    285           <para>Here are examples of paths that contain empty values:</para>
    286 
    287           <itemizedlist>
    288             <listitem>
    289               <para><literal>/usr/share/man:</literal></para>
    290             </listitem>
    291 
    292             <listitem>
    293               <para><literal>:/usr/share/man</literal></para>
    294             </listitem>
    295 
    296             <listitem>
    297               <para><literal>/usr/share/man::/usr/X11R6/man</literal></para>
    298             </listitem>
    299           </itemizedlist>
    300         </note>
    301       </listitem>
    302 
    303       <listitem>
    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>
     295        <para>Here are some examples of paths that contain empty
     296        values:</para>
     297
     298        <simplelist>
     299          <member>/usr/share/man:</member>
     300
     301          <member>:/usr/share/man</member>
     302
     303          <member>/usr/share/man::/usr/X11R6/man</member>
     304        </simplelist>
     305      </listitem>
     306
     307      <listitem>
     308        <para>A DISPLAY variable for X11 application support is set as shown
     309        only for Mac OS X versions 10.4 (Tiger) and earlier if a DISPLAY
     310        variable is not already set in a <filename>.profile</filename> active
     311        at installation time. A DISPLAY variable is never set for Mac OS X
     312        10.5 (Leopard) or higher.</para>
    309313
    310314        <programlisting>export DISPLAY=:0.0</programlisting>
     
    312316    </itemizedlist>
    313317
    314     <para>Changes to <filename>~/.profile</filename> do not take effect until
    315     a new terminal session is opened. Type <command>env</command> in the
    316     terminal to verify the current environment settings. Example output for
    317     the <command>env</command> command is shown below.</para>
     318    <note>
     319      <para>Changes to <filename>~/.profile</filename> do not take effect
     320      until a new terminal session is opened. Type <command>env</command> in
     321      the terminal to verify the current environment settings. Example output
     322      for the <command>env</command> command is shown below.</para>
     323    </note>
    318324
    319325    <screen>MANPATH=
     
    333339SECURITYSESSIONID=b0cea0
    334340_=/usr/bin/env</screen>
    335 
    336     <note>
    337       <para>If you have either a <filename>.bash_login</filename> or a
    338       <filename>.bash_profile</filename> file in your home directory, they may
    339       take precedence over <filename>.profile</filename>. You may either
    340       remove the previously used file, or add the contents of
    341       <filename>.profile</filename> to it.</para>
    342     </note>
    343341  </section>
    344342</chapter>
Note: See TracChangeset for help on using the changeset viewer.