Changeset 45512 for trunk/doc-new


Ignore:
Timestamp:
Jan 16, 2009, 9:16:24 PM (10 years ago)
Author:
markd@…
Message:

Straiten out a wording error and other minor changes in xcode tools section.

File:
1 edited

Legend:

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

    r44116 r45512  
    9797      <listitem>
    9898        <para>Always make sure to install the latest version of Xcode Tools
    99         for your Mac OS X release. Apple's Developer Connection site has a
    100         link for the <ulink
     99        for your Mac OS X release because using earlier versions of Xcode
     100        Tools may cause port install failures. Apple's Developer Connection
     101        site has a link for the <ulink
    101102        url="http://developer.apple.com/technology/xcode.html">latest version
    102         of Xcode Tools</ulink> for the currently shipping release of Mac OS X,
    103         because earlier versions of Xcode Tools may cause port install
    104         failures. To download the latest Xcode Tools version for Mac OS X 10.4
    105         (2.5) or 10.3 (1.5), see the Developer Connection links <ulink
     103        of Xcode Tools</ulink> for the currently shipping release of Mac OS X.
     104        To download the latest Xcode Tools version for Mac OS X 10.4 (v2.5) or
     105        10.3 (v1.5), see the Developer Connection links <ulink
    106106        url="http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=19907">here</ulink>
    107107        and <ulink url="http://connect.apple.com/">here</ulink>
     
    206206        </listitem>
    207207      </orderedlist>
    208    
    209       </section>
    210 
    211       <section id="installing.macports.subversion">
    212         <title>Subversion Install</title>
    213 
    214         <para>
    215           If you installed MacPorts using the package installer, skip this                                                   
    216           section.
    217         </para>
    218 
    219         <para>
    220           There are times when some may want to run MacPorts from a version newer
    221           than the current stable release. Maybe there's a new feature that you'd
    222           like to use, or it fixes an issue you've encountered, or you just like
    223           to be on the cutting edge. These steps explain how to run completely from trunk,
    224           using only Subversion to keep MacPorts up to date.
    225         </para>
    226 
    227         <orderedlist>
    228           <listitem>
    229             <para>Check out MacPorts source</para>
    230             <para>
    231               Pick a location to store a working copy of the MacPorts code. For this example,
    232               <filename>/opt/mports</filename> will be used, but you can put the source anywhere.
    233               This example will create <filename>/opt/mports/trunk</filename> containing
    234               everything needed for MacPorts.
    235             </para>
    236             <programlisting><prompt>%%</prompt> <userinput>mkdir -p /opt/mports</userinput>
     208    </section>
     209
     210    <section id="installing.macports.subversion">
     211      <title>Subversion Install</title>
     212
     213      <para>If you installed MacPorts using the package installer, skip this
     214      section.</para>
     215
     216      <para>There are times when some may want to run MacPorts from a version
     217      newer than the current stable release. Maybe there's a new feature that
     218      you'd like to use, or it fixes an issue you've encountered, or you just
     219      like to be on the cutting edge. These steps explain how to run
     220      completely from trunk, using only Subversion to keep MacPorts up to
     221      date.</para>
     222
     223      <orderedlist>
     224        <listitem>
     225          <para>Check out MacPorts source</para>
     226
     227          <para>Pick a location to store a working copy of the MacPorts code.
     228          For this example, <filename>/opt/mports</filename> will be used, but
     229          you can put the source anywhere. This example will create
     230          <filename>/opt/mports/trunk</filename> containing everything needed
     231          for MacPorts.</para>
     232
     233          <programlisting><prompt>%%</prompt> <userinput>mkdir -p /opt/mports</userinput>
    237234<prompt>%%</prompt> <userinput>cd /opt/mports</userinput>
    238235<prompt>%%</prompt> <userinput>svn checkout http://svn.macports.org/repository/macports/trunk</userinput></programlisting>
    239             <note>
    240               You only really need the base subdirectory to run MacPorts, so you can avoid checking out
    241               the rest if you don't want to use a Subversion-based ports tree (see Step 3 below). To just get
    242               the base directory, append <filename>/base</filename> to the end of the svn checkout command
    243               above. The resulting directory will then be <filename>/opt/mports/base</filename>
    244             </note>
    245           </listitem>
    246 
    247           <listitem>
    248             <para>Build and Install MacPorts</para>
    249             <para>
    250               MacPorts uses autoconf and makefiles for installation. These commands will build
    251               and install MacPorts to <filename>/opt/local</filename>. You can add the
    252               <option>--prefix</option> option to <filename>./configure</filename> to relocate
    253               MacPorts to another directory if needed.
    254             </para>
    255             <programlisting><prompt>%%</prompt> <userinput>cd /opt/mports/trunk/base</userinput>
     236
     237          <note>
     238             You only really need the base subdirectory to run MacPorts, so you can avoid checking out the rest if you don't want to use a Subversion-based ports tree (see Step 3 below). To just get the base directory, append
     239
     240            <filename>/base</filename>
     241
     242             to the end of the svn checkout command above. The resulting directory will then be
     243
     244            <filename>/opt/mports/base</filename>
     245
     246             
     247          </note>
     248        </listitem>
     249
     250        <listitem>
     251          <para>Build and Install MacPorts</para>
     252
     253          <para>MacPorts uses autoconf and makefiles for installation. These
     254          commands will build and install MacPorts to
     255          <filename>/opt/local</filename>. You can add the
     256          <option>--prefix</option> option to <filename>./configure</filename>
     257          to relocate MacPorts to another directory if needed.</para>
     258
     259          <programlisting><prompt>%%</prompt> <userinput>cd /opt/mports/trunk/base</userinput>
    256260<prompt>%%</prompt> <userinput>./configure --enable-readline</userinput>
    257261<prompt>%%</prompt> <userinput>make</userinput>
    258262<prompt>%%</prompt> <userinput>sudo make install</userinput>
    259263<prompt>%%</prompt> <userinput>make distclean</userinput></programlisting>
    260           </listitem>
    261 
    262           <listitem>
    263             <para>(Optional) Configure MacPorts to use port information from Subversion</para>
    264             <para>
    265               This step is useful if you want to do port development.
    266               Open <filename>/opt/local/etc/macports/sources.conf</filename> in a text editor.
    267               The last line which should look like this:
    268             </para>
    269             <programlisting>rsync://rsync.macports.org/release/ports/</programlisting>
    270             <para>Change it to point to the working copy you checked out:</para>           
    271             <programlisting>file:///opt/mports/trunk/dports</programlisting>
    272             <para>Now MacPorts will look for portfiles in the working copy.</para>
    273           </listitem>
    274 
    275           <listitem>
    276             <para>Environment</para>
    277             <para>
    278               You should setup your PATH and other environment options according to
    279               the <link linkend="installing.shell">following section</link>.
    280             </para>
    281           </listitem>
    282         </orderedlist>
    283       </section>
    284 
    285       <section id="installing.macports.source.multiple">
    286         <title>Install Multiple MacPorts Copies</title>
    287 
    288         <para>Occasionally a MacPorts developer may wish to install more than
    289         one MacPorts instance on the same host. Only one copy of MacPorts may
    290         use the default Tcl library path <filename>/Library/Tcl/</filename>,
    291         so for additional installations use the option
    292         <option>--with-tclpackage</option> as shown below and substitute
    293         NEW_TCL_PACKAGE with any empty directory, for example
    294         <filename>/Library/Tcl/macports-new/</filename>.</para>
    295 
    296         <note>
    297           <para>The first command temporarily removes the standard MacPorts
    298           binary paths because they must not be present while installing a
    299           second instance.</para>
    300         </note>
    301 
    302         <programlisting><prompt>%%</prompt> <userinput>export PATH=/bin:/sbin:/usr/bin:/usr/sbin</userinput>
     264        </listitem>
     265
     266        <listitem>
     267          <para>(Optional) Configure MacPorts to use port information from
     268          Subversion</para>
     269
     270          <para>This step is useful if you want to do port development. Open
     271          <filename>/opt/local/etc/macports/sources.conf</filename> in a text
     272          editor. The last line which should look like this:</para>
     273
     274          <programlisting>rsync://rsync.macports.org/release/ports/</programlisting>
     275
     276          <para>Change it to point to the working copy you checked out:</para>
     277
     278          <programlisting>file:///opt/mports/trunk/dports</programlisting>
     279
     280          <para>Now MacPorts will look for portfiles in the working
     281          copy.</para>
     282        </listitem>
     283
     284        <listitem>
     285          <para>Environment</para>
     286
     287          <para>You should setup your PATH and other environment options
     288          according to the <link linkend="installing.shell">following
     289          section</link>.</para>
     290        </listitem>
     291      </orderedlist>
     292    </section>
     293
     294    <section id="installing.macports.source.multiple">
     295      <title>Install Multiple MacPorts Copies</title>
     296
     297      <para>Occasionally a MacPorts developer may wish to install more than
     298      one MacPorts instance on the same host. Only one copy of MacPorts may
     299      use the default Tcl library path <filename>/Library/Tcl/</filename>, so
     300      for additional installations use the option
     301      <option>--with-tclpackage</option> as shown below and substitute
     302      NEW_TCL_PACKAGE with any empty directory, for example
     303      <filename>/Library/Tcl/macports-new/</filename>.</para>
     304
     305      <note>
     306        <para>The first command temporarily removes the standard MacPorts
     307        binary paths because they must not be present while installing a
     308        second instance.</para>
     309      </note>
     310
     311      <programlisting><prompt>%%</prompt> <userinput>export PATH=/bin:/sbin:/usr/bin:/usr/sbin</userinput>
    303312<prompt>%%</prompt> <userinput>cd ~/MacPorts-1.x.x/</userinput>
    304313<prompt>%%</prompt> <userinput>./configure --prefix=NEW_PREFIX --with-tclpackage=NEW_TCLPACKAGE</userinput>
     
    306315<prompt>%%</prompt> <userinput>sudo make install</userinput>
    307316</programlisting>
    308       </section>
    309     </section>
    310 
    311     <section id="installing.macports.upgrade">
    312       <title>MacPorts Upgrade</title>
    313 
    314       <para>MacPorts base upgrades are performed automatically (when a newer
    315       release is available) during a <link
    316       linkend="using.port.selfupdate">selfupdate</link> operation. To upgrade
    317       a copy of MacPorts that was installed from source to the newer release
    318       of the source code, simply repeat the <link
    319       linkend="installing.macports.source">source install</link> with the
    320       newer version of the MacPorts source code.</para>
    321     </section>
    322 
    323     <section id="installing.macports.uninstalling">
    324       <title>Uninstall</title>
    325 
    326       <para>To uninstall MacPorts from the default location
    327       <filename>/opt/local/</filename>, perform this command from a terminal
    328       window.</para>
    329 
    330       <programlisting><prompt>%%</prompt> <userinput>sudo rm -rf \
     317    </section>
     318  </section>
     319
     320  <section id="installing.macports.upgrade">
     321    <title>MacPorts Upgrade</title>
     322
     323    <para>MacPorts base upgrades are performed automatically (when a newer
     324    release is available) during a <link
     325    linkend="using.port.selfupdate">selfupdate</link> operation. To upgrade a
     326    copy of MacPorts that was installed from source to the newer release of
     327    the source code, simply repeat the <link
     328    linkend="installing.macports.source">source install</link> with the newer
     329    version of the MacPorts source code.</para>
     330  </section>
     331
     332  <section id="installing.macports.uninstalling">
     333    <title>Uninstall</title>
     334
     335    <para>To uninstall MacPorts from the default location
     336    <filename>/opt/local/</filename>, perform this command from a terminal
     337    window.</para>
     338
     339    <programlisting><prompt>%%</prompt> <userinput>sudo rm -rf \
    331340    /opt/local \
    332341    /etc/manpaths.d/macports \
Note: See TracChangeset for help on using the changeset viewer.