New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Changeset 81650


Ignore:
Timestamp:
08/03/11 05:36:49 (4 years ago)
Author:
jmr@…
Message:

guide: update to reflect that .profile is not the only shell config file we handle

File:
1 edited

Legend:

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

    r81649 r81650  
    425425    <title>MacPorts and the Shell</title> 
    426426 
    427     <para>MacPorts requires that some environmental variables be set in the 
     427    <para>MacPorts requires that some environment variables be set in the 
    428428    shell. When MacPorts is installed using the Mac OS X package installer, a 
    429429    <quote>postflight</quote> script is run after installation that 
    430     automatically copies a <filename>.profile</filename> containing variables 
     430    automatically adds or modifies a shell configuration file in your home directory, 
     431    ensuring that it defines variables 
    431432    according to the rules described in the following section. Those <link 
    432433    linkend="installing.macports.source">installing MacPorts from source 
     
    434435    guide.</para> 
    435436 
    436     <note> 
    437       <para>If you have either a <filename>.bash_login</filename> or a 
    438       <filename>.bash_profile</filename> file in your home directory, they may 
    439       take precedence over <filename>.profile</filename>. You may either 
    440       remove the previously used file, or add the contents of 
    441       <filename>.profile</filename> to it.</para> 
    442     </note> 
     437    <para>Depending on your shell and which configuration files already exist, the 
     438    installer may use <filename>.profile</filename>, <filename>.bash_login</filename>, 
     439    <filename>.bash_profile</filename>, <filename>.tcshrc</filename>, or 
     440    <filename>.cshrc</filename>.</para> 
    443441 
    444442    <section id="installing.shell.postflight"> 
    445443      <title>The Postflight Script</title> 
    446444 
    447       <para>The postflight script automatically copies a 
    448       <filename>.profile</filename> containing the <varname>PATH</varname> 
     445      <para>The postflight script automatically sets 
     446      the <varname>PATH</varname> 
    449447      variable, and optionally the <varname>MANPATH</varname> and 
    450448      <varname>DISPLAY</varname> variables according to the rules described 
    451       below. If a current <filename>.profile</filename> file exists at 
     449      below. If a current shell configuration file exists at 
    452450      installation time it is renamed to <quote>mpsaved_$timestamp</quote>. 
    453451      Those <link linkend="installing.macports.source">installing MacPorts 
     
    509507 
    510508          <para>Condition: If installing on a Mac OS X version earlier than 
    511           10.5 (Leopard), and if a <filename>.profile</filename> file exists 
     509          10.5 (Leopard), and if a shell configuration file exists 
    512510          at time of MacPorts installation without a 
    513511          <varname>DISPLAY</varname> variable, the postflight script sets a 
     
    522520 
    523521    <section id="installing.shell.verifyprofile"> 
    524       <title>Verify the .profile</title> 
    525  
    526       <para>To verify that the <filename>.profile</filename> containing the 
     522      <title>Verify the configuration file</title> 
     523 
     524      <para>To verify that the file containing the 
    527525      MacPorts variables is in effect, type <command>env</command> in the 
    528526      terminal to verify the current environment settings after the 
    529       <filename>.profile</filename> has been created. Example output for the 
     527      file has been created. Example output for the 
    530528      <command>env</command> command is shown below.</para> 
    531529 
    532530      <note> 
    533         <para>Changes to <filename>~/.profile</filename> do not take effect 
     531        <para>Changes to shell configuration files do not take effect 
    534532        until a new terminal session is opened.</para> 
    535533      </note> 
     
    565563 
    566564      <para>For example, to use the nano editor, add this line to your 
    567       <filename>~/.profile</filename>:</para> 
     565      bash config:</para> 
    568566 
    569567      <programlisting>export EDITOR=/usr/bin/nano</programlisting> 
     
    571569      <para>To use the user-friendly GUI editor <ulink 
    572570      url="http://www.barebones.com/products/textwrangler/">TextWrangler</ulink> 
    573       (installation required), add this line to your 
    574       <filename>~/.profile</filename>:</para> 
     571      (installation required), add this line:</para> 
    575572 
    576573      <programlisting>export EDITOR=/usr/bin/edit</programlisting> 
    577574       
    578       <para>To keep a text editor as default while using a graphic editor with 
    579       portfiles add this to <filename>~/.profile</filename>: </para> 
     575      <para>To keep a command-line text editor as default while using a graphic editor with 
     576      portfiles, add this: </para> 
    580577 
    581578      <programlisting> 
Note: See TracChangeset for help on using the changeset viewer.