Changeset 26404 for trunk/doc


Ignore:
Timestamp:
Jun 21, 2007, 8:53:47 AM (12 years ago)
Author:
boeyms@…
Message:

Pick off some low-hanging fruit to start updating the DocBook documentation:

  • Replace instances of "Darwinports" with "MacPorts", "dport" with "mport", "CVS" with "Subversion" and "cvs" with "svn";
  • Update some of the old email address and links;
  • Make one update about MacPorts no longer supporting OSes other than Mac OS 10.3 and above.
Location:
trunk/doc
Files:
23 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/faq/Makefile

    r19639 r26404  
    11# $Id$
    22
    3 # To build DarwinPorts FAQ files from the source docbook xml.
     3# To build MacPorts FAQ files from the source docbook xml.
    44# michaelm@opendarwin.org, wbb4@opendarwin.org
    55
  • trunk/doc/faq/resources/docbook.css

    r19376 r26404  
    11/*
    2  * DarwinPorts Guide Stylesheet
     2 * MacPorts Guide Stylesheet
    33 */
    44
  • trunk/doc/faq/xml/faq.xml

    r26302 r26404  
    55<article>
    66  <articleinfo>
    7     <title>DarwinPorts FAQ</title>
     7    <title>MacPorts FAQ</title>
    88
    99                <author>
     
    3232
    3333        <abstract>
    34                 <para>The DarwinPorts Frequently Asked Questions will attempt to
    35                         answer some questions that are often asked about DarwinPorts.</para>
     34                <para>The MacPorts Frequently Asked Questions will attempt to
     35                        answer some questions that are often asked about MacPorts.</para>
    3636        </abstract>
    3737
     
    4242                        <qandaentry>
    4343                                <question>
    44                                         <para>What IS DarwinPorts?</para>
     44                                        <para>What IS MacPorts?</para>
    4545                                </question>
    4646
    4747                                <answer>
    48                                         <para>DarwinPorts is probably best described by comparison:  It's
     48                                        <para>MacPorts is probably best described by comparison:  It's
    4949                                                sort of like the FreeBSD ports collection or fink in
    5050                                                that it automates the process of building 3rd party
     
    5252                                                information for a given piece of software and knows how to
    5353                                                make it build under Mac OS X and install it to a common
    54                                                 location, meaning that software installed via DarwinPorts
     54                                                location, meaning that software installed via MacPorts
    5555                                                doesn't simply scatter itself all over the system or
    5656                                                require user knowledge of what to install in what order.</para>
     
    6060                        <qandaentry>
    6161                                <question>
    62                                         <para>How does DarwinPorts compare to FreeBSD ports?</para>
     62                                        <para>How does MacPorts compare to FreeBSD ports?</para>
    6363                                </question>
    6464               
     
    7777                        <qandaentry>
    7878                                <question>
    79                                         <para>Why did DarwinPorts start from scratch rather than
     79                                        <para>Why did MacPorts start from scratch rather than
    8080                                        adopting something like FreeBSD ports?</para>
    8181                                </question>
     
    8787                                        looks at first glance and         there's always room for
    8888                                        fresh approaches to the problem, which         is what we set
    89                                         out to do with DarwinPorts. There are certainly         other
     89                                        out to do with MacPorts. There are certainly         other
    9090                                        systems, some of which have already been mentioned, which
    9191                                        have made their own attempts at solving this problem and there
     
    9595                                        programmin language which pleases         everyone - it's more
    9696                                        or less impossible.  We urge people to         judge
    97                                         DarwinPorts' design on its own merits and consider it a
     97                                        MacPorts' design on its own merits and consider it a
    9898                                        parallel rather than a competing effort since there's more
    9999                                        software out there than any one system can ever manage to
     
    104104                        <qandaentry>
    105105                                <question>
    106                                         <para>Will DarwinPorts run on any other Operating System?</para>
     106                                        <para>Will MacPorts run on any other Operating System?</para>
    107107                                </question>
    108108               
    109109                                <answer>
    110                                         <para>DarwinPorts was designed to be as portable as possible.
     110                                        <para>MacPorts was designed to be as portable as possible.
    111111                                        Though our target platforms are Mac OS X and Darwin,
    112                                         DarwinPorts is known to work on FreeBSD, OpenBSD, NetBSD and
     112                                        MacPorts is known to work on FreeBSD, OpenBSD, NetBSD and
    113113                                        Solaris.  We also provide individual ports with ways of
    114114                                        specifying platform-specific rules that are only invoked on
     
    119119                        <qandaentry>
    120120                                <question>
    121                                         <para>Does DarwinPorts also do Package Management?</para>
     121                                        <para>Does MacPorts also do Package Management?</para>
    122122                                </question>
    123123               
    124124                                <answer>
    125                                         <para>DarwinPorts works by first building software and
     125                                        <para>MacPorts works by first building software and
    126126                                        installing it into a <varname>destroot</varname>, a
    127127                                        fake-installation location, then installing it into the
    128                                         DarwinPorts prefix (<filename>/opt/local</filename> by
     128                                        MacPorts prefix (<filename>/opt/local</filename> by
    129129                                        default).  It records this installation in its registry, and
    130130                                        you can query the installed port and uninstall it through
    131                                         DarwinPorts.  Work is underway to add full package management
    132                                         features to DarwinPorts.</para>
     131                                        MacPorts.  Work is underway to add full package management
     132                                        features to MacPorts.</para>
    133133
    134                                         <para>You can also have DarwinPorts build a Mac OS X
     134                                        <para>You can also have MacPorts build a Mac OS X
    135135                                        <filename>.pkg</filename> file of the port, and install it
    136136                                        using the Mac OS X Installer.  If that package has
    137137                                        dependencies, then you can also build a multi-part package
    138138                                        (<filename>.mpkg</filename>) which contains them as well.  You
    139                                         can also build RPM packages from DarwinPorts.</para>
     139                                        can also build RPM packages from MacPorts.</para>
    140140                                </answer>
    141141                        </qandaentry>
     
    143143                        <qandaentry>
    144144                                <question>
    145                                         <para>Why does DarwinPorts install everything into
     145                                        <para>Why does MacPorts install everything into
    146146                                        <filename>/opt/local</filename> by default?</para>
    147147                                </question>
     
    151151                                        editing /etc/ports/ports.conf or specifying
    152152                                        <varname>--prefix</varname> during the
    153                                         <filename>./configure</filename> phase of the DarwinPorts
     153                                        <filename>./configure</filename> phase of the MacPorts
    154154                                        installation, so nothing           is fixed
    155                                         in place.  Even the basic DarwinPorts infrastructure,
     155                                        in place.  Even the basic MacPorts infrastructure,
    156156                                        which installs into /opt/local by           default, can be
    157157                                        installed elsewhere by overriding the value of
  • trunk/doc/guide/Makefile

    r19376 r26404  
    11# $Id$
    22
    3 # To build DarwinPorts  guide files from the source docbook xml.
     3# To build MacPorts  guide files from the source docbook xml.
    44# michaelm@opendarwin.org
    55
  • trunk/doc/guide/resources/docbook.css

    r19376 r26404  
    11/*
    2  * DarwinPorts Guide Stylesheet
     2 * MacPorts Guide Stylesheet
    33 */
    44
  • trunk/doc/guide/xml/guide.xml

    r26302 r26404  
    55<book xmlns:xi="http://www.w3.org/2001/XInclude">
    66  <bookinfo>
    7     <title>DarwinPorts Guide</title>
     7    <title>MacPorts Guide</title>
    88     
    99    <author>
     
    2626
    2727                <legalnotice>
    28                         <para>If you have any questions regarding DarwinPorts, you may
    29                                 email the DarwinPorts mailing list:
     28                        <para>If you have any questions regarding MacPorts, you may
     29                                email the MacPorts mailing list:
    3030                                <ulink
    31                                                 url="mailto:darwinports@opendarwin.org">
    32                                         darwinports@opendarwin.org
     31                                                url="mailto:macports-users@lists.macosforge.org">
     32                                        macports-users@opendarwin.org
    3333                                </ulink>
    3434                                Please be aware that you are not allowed mail to the list
     
    3636                                subscribe to the list here:
    3737                                <ulink
    38                                                 url="http://www.opendarwin.org/mailman/listinfo/darwinports">
    39                                                 OpenDarwin mailman: DarwinPorts
     38                                                url="http://www.opendarwin.org/mailman/listinfo/macports">
     39                                                MacOSforge mailman: MacPorts
    4040                                </ulink>
    4141                        </para>
     
    5353    <title>About this guide</title>
    5454      <para>Part I of this guide is intended to help you use
    55         the DarwinPorts system. Part II is directed towards
    56         users who wish to add their favorite software to DarwinPorts.
     55        the MacPorts system. Part II is directed towards
     56        users who wish to add their favorite software to MacPorts.
    5757        Part III is intended for developers interested in extending
    58         the DarwinPorts system.</para>
     58        the MacPorts system.</para>
    5959
    6060      <para>The Guide is still at an early draft stage, so if you have any
    6161        comments, corrections or (even better) contributions, please
    62         contact the OpenDarwin Documentation Project at
    63         <email>doc@opendarwin.org</email>.</para>
     62        contact the MacPorts Documentation Project at
     63        <email>macports-docs@lists.macosforge.org</email>.</para>
    6464  </preface>
    6565
    6666  <part>
    67     <title>Using DarwinPorts</title>
     67    <title>Using MacPorts</title>
    6868
    6969    <xi:include href="user/user.xml" />
     
    7474
    7575  <part>
    76     <title>DarwinPorts Portfiles</title>
     76    <title>MacPorts Portfiles</title>
    7777   
    7878    <xi:include href="portfiles/quick.xml" />
     
    9595
    9696  <part>
    97     <title>DarwinPorts Internals</title>
     97    <title>MacPorts Internals</title>
    9898 
    9999    <xi:include href="internals/internals.xml" />
     
    103103
    104104        <part>
    105                 <title>The DarwinPorts Project</title>
     105                <title>The MacPorts Project</title>
    106106
    107107                <xi:include href="project/info.xml" />
  • trunk/doc/guide/xml/internals/internals.xml

    r26302 r26404  
    1010  </chapterinfo>
    1111 
    12   <title>DarwinPorts APIs</title>
     12  <title>MacPorts APIs</title>
    1313
    1414  <sect1 id="about">
    1515    <title>About This Chapter</title>
    1616
    17     <para>DarwinPorts contains two application programming interfaces
     17    <para>MacPorts contains two application programming interfaces
    1818    (APIs), written in Tcl.</para>
    1919   
    2020    <para>The Ports API is an internal API used to run individual
    21       Portfiles.  The DarwinPorts (dport*) API is a high-level API used by
    22       client applications such as DarwinPorts Manager.app or
     21      Portfiles.  The MacPorts (mport*) API is a high-level API used by
     22      client applications such as MacPorts Manager.app or
    2323      <command>port</command>.</para>
    2424  </sect1>
     
    7878
    7979  <sect1 id="dp_api">
    80     <title>DarwinPorts API</title>
    81 
    82     <para>The code for the DarwinPorts API is located in
    83       base/src/darwinports1.0. The DarwinPorts API performs the
     80    <title>MacPorts API</title>
     81
     82    <para>The code for the MacPorts API is located in
     83      base/src/macports1.0. The MacPorts API performs the
    8484      following functions:</para>
    8585
     
    109109          <para>Registry management routines. Manages the rudimentary
    110110            port registry in
    111             <filename>${prefix}/var/db/dports/receipts/</filename>.</para>
     111            <filename>${prefix}/var/db/mports/receipts/</filename>.</para>
    112112
    113113          <para>
    114114            <itemizedlist>
    115115              <listitem>
    116                 <para><function>dportregistry::new</function>: create a
     116                <para><function>mportregistry::new</function>: create a
    117117                  new port registry entry</para>
    118118              </listitem>
    119119
    120120              <listitem>
    121                 <para><function>dportregistry::exists</function>: check
     121                <para><function>mportregistry::exists</function>: check
    122122                  if a port registry entry exists (either versioned or
    123123                  not)</para>
     
    125125
    126126              <listitem>
    127                 <para><function>dportregistry::delete</function>: delete
     127                <para><function>mportregistry::delete</function>: delete
    128128                  an existing registry entry</para>
    129129              </listitem>
    130130
    131131              <listitem>
    132                 <para><function>dportregistry::close</function>: closes
     132                <para><function>mportregistry::close</function>: closes
    133133                  a new registry entry</para>
    134134              </listitem>
     
    138138
    139139        <listitem>
    140           <para>Exports the "darwinports" API for use by client
     140          <para>Exports the "macports" API for use by client
    141141            applications:</para>
    142142
     
    144144            <itemizedlist>
    145145              <listitem>
    146                 <para><function>dportinit</function>: Initializes the
    147                   darwinports system. Should be called before trying to
     146                <para><function>mportinit</function>: Initializes the
     147                  macports system. Should be called before trying to
    148148                  use any other procedure</para>
    149149              </listitem>
    150150
    151151              <listitem>
    152                 <para><function>dportsearch</function>: Given a regexp,
     152                <para><function>mportsearch</function>: Given a regexp,
    153153                  searches the PortIndex for ports with matching
    154154                  names</para>
     
    156156
    157157              <listitem>
    158                 <para><function>dportopen</function>: Given a URI to a
     158                <para><function>mportopen</function>: Given a URI to a
    159159                  port, opens the port and returns an opaque handle to
    160160                  it</para>
     
    162162
    163163              <listitem>
    164                 <para><function>dportclose</function>: Given a port
     164                <para><function>mportclose</function>: Given a port
    165165                  handle, closes the port.</para>
    166166              </listitem>
    167167
    168168              <listitem>
    169                 <para><function>dportexec</function>: Given a port
     169                <para><function>mportexec</function>: Given a port
    170170                  handle, executes a target (i.e. install)</para>
    171171              </listitem>
    172172
    173173              <listitem>
    174                 <para><function>dportinfo</function>: Given a port
     174                <para><function>mportinfo</function>: Given a port
    175175                  handle, this returns the PortInfo array (as a flat
    176176                  list of array elements). This is a little tricky and
     
    190190    </para>
    191191   
    192     <para>An example of how the DarwinPorts API is used:</para>
    193 
    194     <para><function>dportsearch</function> returns an arbitrary number
     192    <para>An example of how the MacPorts API is used:</para>
     193
     194    <para><function>mportsearch</function> returns an arbitrary number
    195195      of Tcl arrays containing data from the
    196196      <filename>PortIndex</filename>. The returned data includes the
     
    198198      one executes <userinput>port install cm3</userinput>, the
    199199      <command>port</command> utility uses the
    200       <function>dportsearch</function> function to find the first port
    201       that matches the name "cm3", uses <function>dportopen</function>
    202       to open the port, and then uses <function>dportexec</function> to
     200      <function>mportsearch</function> function to find the first port
     201      that matches the name "cm3", uses <function>mportopen</function>
     202      to open the port, and then uses <function>mportexec</function> to
    203203      execute the install target in the port. Then, it uses
    204       <function>dportclose</function> to close the port. When one
     204      <function>mportclose</function> to close the port. When one
    205205      executes <userinput>port search cm3</userinput>, the port utility
    206       uses <function>dportsearch</function>, takes the list of arrays,
     206      uses <function>mportsearch</function>, takes the list of arrays,
    207207      and formats the data for human consumption.</para>
    208208  </sect1>
  • trunk/doc/guide/xml/internals/portimages.xml

    r26302 r26404  
    1111  </chapterinfo>
    1212 
    13   <title>DarwinPorts Port Images</title>
     13  <title>MacPorts Port Images</title>
    1414
    1515  <sect1 id="about">
    1616    <title>About This Chapter</title>
    1717
    18                 <para>This chapter provides a detailed overview of the DarwinPorts
    19                         Port Images for DarwinPorts Infrastructure developers.</para>
     18                <para>This chapter provides a detailed overview of the MacPorts
     19                        Port Images for MacPorts Infrastructure developers.</para>
    2020  </sect1>
    2121
  • trunk/doc/guide/xml/internals/registry.xml

    r26302 r26404  
    1111  </chapterinfo>
    1212 
    13   <title>The DarwinPorts Registry</title>
     13  <title>The MacPorts Registry</title>
    1414
    1515  <sect1 id="about">
    1616    <title>About This Chapter</title>
    1717
    18                 <para>This chapter provides a detailed overview of the new DarwinPorts
     18                <para>This chapter provides a detailed overview of the new MacPorts
    1919                        Registry package and its API.  This package is queried by the
    20                         DarwinPorts tools for information about installed ports for
     20                        MacPorts tools for information about installed ports for
    2121                        information related to dependencies, port images, and simple user
    2222                        information about what is installed.</para>
    2323
    24                 <para>The DarwinPorts Registry contains an abstraction layer which
     24                <para>The MacPorts Registry contains an abstraction layer which
    2525                        allows for alternative storage mechanisms for receipts.  This
    2626                        chapter will also provide an overview of this, and how to write a
     
    3131                <title>Introduction To The New Registry</title>
    3232
    33                 <para>The new DarwinPorts Registry solves many problems with the old
     33                <para>The new MacPorts Registry solves many problems with the old
    3434                        registry:</para>
    3535
     
    4848                <para>The new registry allows for modification of receipts, to
    4949                        reflect and changes made to installed ports being maintained by
    50                         DarwinPorts.  It also provides global file and dependencies
     50                        MacPorts.  It also provides global file and dependencies
    5151                        databases that can be queried to check if installed files conflict
    5252                        with each other, and to maintain dependency trees of installed
     
    5959                <title>API For Accessing The Registry</title>
    6060
    61                 <para>The DarwinPorts Registry provides a public API in the
     61                <para>The MacPorts Registry provides a public API in the
    6262                        <varname>registry1.0</varname> Tcl package.  Using this API you
    63                         can access the DarwinPorts Registry using the storage mechanism
    64                         the DarwinPorts user has chosen for receipt storage.</para>
     63                        can access the MacPorts Registry using the storage mechanism
     64                        the MacPorts user has chosen for receipt storage.</para>
    6565
    6666                <variablelist>
  • trunk/doc/guide/xml/portfiles/commands.xml

    r26302 r26404  
    137137
    138138    <sect2>
    139       <title>CVS Options</title>
     139      <title>Subversion Options</title>
    140140
    141141      <para></para>
  • trunk/doc/guide/xml/portfiles/details.xml

    r26302 r26404  
    9191                                <term>libpath</term>
    9292                                <listitem>
    93                                         <para>Path to the DarwinPorts TCL libraries. Read only.</para>
     93                                        <para>Path to the MacPorts TCL libraries. Read only.</para>
    9494                                       
    9595                                </listitem>
     
    190190                                <listitem>
    191191                                        <para>Determines which version of the portsystem the
    192                                         Portfile is compatible with. DarwinPorts supports
     192                                        Portfile is compatible with. MacPorts supports
    193193                                        versioning of the PortSystem so if new, backwards
    194194                                        incompatible changes are introduced older Portfiles
    195195                                        can continue to use the older version of the system.
    196196                                        The PortSystem line wraps the loading of TCL libraries
    197                                         appropriate for that version of DarwinPorts. If you
     197                                        appropriate for that version of MacPorts. If you
    198198                                        don't load the libraries, nothing else in the Portfile
    199199                                        will work. Thus, the PortSystem should be the top line
    200200                                        in the Portfile.</para>
    201201                                       
    202                                         <para>Currently DarwinPorts only has version 1.0 so you
     202                                        <para>Currently MacPorts only has version 1.0 so you
    203203                                        should put: <userinput>PortSystem 1.0</userinput> in your
    204204                                        Portfile.</para>
     
    472472              download which file from.</para>
    473473           
    474             <para>Fortunately DarwinPorts also provides a much more
     474            <para>Fortunately MacPorts also provides a much more
    475475              powerful and flexible syntax for mirror site lists.</para>
    476476
     
    554554              <listitem><para><varname>kde</varname></para></listitem>
    555555              <listitem><para><varname>openbsd</varname></para></listitem>
    556               <listitem><para><varname>opendarwin</varname></para></listitem>
    557556              <listitem><para><varname>perl_cpan</varname></para></listitem>
    558557              <listitem><para><varname>postgresql</varname></para></listitem>
     
    951950                  install correctly into the destroot.</para>
    952951                <para>All ports must install via the 'destroot' so
    953                   that the DarwinPorts infrastructure can register each
     952                  that the MacPorts infrastructure can register each
    954953                  file and directory a port installs. Most autoconf based
    955954                  build systems will behave correctly and respect DESTDIR,
     
    11301129        <sect1>
    11311130          <title>TCL primitives</title>
    1132           <para>DarwinPorts provides several useful TCL primitives for
     1131          <para>MacPorts provides several useful TCL primitives for
    11331132            use within Portfiles.</para>
    11341133
  • trunk/doc/guide/xml/portfiles/hier.xml

    r26302 r26404  
    1212                installed conforms to specific filesystem hierarchy guidelines.
    1313                These guidelines define where certain files should be installed in
    14                 the DarwinPorts filesystem.</para>
     14                the MacPorts filesystem.</para>
    1515        </sect1>
    1616       
    1717        <sect1>
    18                 <title>DarwinPorts Base, ${prefix}</title>
     18                <title>MacPorts Base, ${prefix}</title>
    1919
    2020                <variablelist>
     
    2323
    2424                                <listitem>
    25                                         <para>The base of the DarwinPorts filesystem
     25                                        <para>The base of the MacPorts filesystem
    2626                                        hierarchy.</para>
    2727
     
    156156                                                                                        <variablelist>
    157157                                                                                                <varlistentry>
    158                                                                                                         <term><filename>dports/</filename></term>
    159 
    160                                                                                                         <listitem><para>DarwinPorts runtime
     158                                                                                                        <term><filename>mports/</filename></term>
     159
     160                                                                                                        <listitem><para>MacPorts runtime
    161161                                                                                                        data.</para></listitem>
    162162                                                                                                </varlistentry>
  • trunk/doc/guide/xml/portfiles/quick.xml

    r26302 r26404  
    2222
    2323  <sect1 id="getting_started">
    24     <title>Getting Started With DarwinPorts</title>
     24    <title>Getting Started With MacPorts</title>
    2525
    2626    <para>This document will provide a short guide to the basics of a
    27       DarwinPorts <filename>Portfile</filename>.  A
     27      MacPorts <filename>Portfile</filename>.  A
    2828      <filename>Portfile</filename> is actually a Tcl script run by the
    2929      <command>port</command> system.  Despite this, the
     
    3131      straightforward.</para>
    3232   
    33     <para>In order to work with DarwinPorts, you will need to download and
    34       install it on your system.  The <link linkend='getting_dports'>
    35       Obtaining</link> and <link linkend='install_dports'>Installing 
    36       DarwinPorts</link> sections of this guide describes the process in
     33    <para>In order to work with MacPorts, you will need to download and
     34      install it on your system.  The <link linkend='getting_mports'>
     35      Obtaining</link> and <link linkend='install_mports'>Installing 
     36      MacPorts</link> sections of this guide describes the process in
    3737      detail. </para>
    3838
     
    4242      output) and the <option>-d</option> (debugging option) switches.
    4343      This will display useful messages that are usually suppressed
    44       while running DarwinPorts.</para>
     44      while running MacPorts.</para>
    4545  </sect1>
    4646
     
    9191              <varname>#&#x0024;Id: &#x0024;</varname>. This is a RCS
    9292              <varname>Id</varname> tag (commented out with the '#' character
    93               so that DarwinPorts is not confused by the tag). </para>
     93              so that MacPorts is not confused by the tag). </para>
    9494          </listitem>
    9595        </varlistentry>
     
    171171      </variablelist>
    172172     
    173       <para>DarwinPorts uses the terms 'keys' and 'options'
     173      <para>MacPorts uses the terms 'keys' and 'options'
    174174        interchangeably since most keys are used as options of a
    175175        particular task in the porting process.</para>
    176176     
    177177      <para>At this point, the <filename>Portfile</filename> is complete
    178         enough to download ircII.  By default, DarwinPorts will append
     178        enough to download ircII.  By default, MacPorts will append
    179179        the <varname>version</varname> to <varname>name</varname> and
    180180        assume sources are in a gzipped tar archive with the
     
    190190      <para><computeroutput><literallayout>DEBUG: Executing com.apple.main (ircii)
    191191DEBUG: Executing com.apple.fetch (ircii)
    192 --->  ircii-20020912.tar.gz doesn't seem to exist in /opt/local/var/db/dports/distfiles
     192--->  ircii-20020912.tar.gz doesn't seem to exist in /opt/local/var/db/mports/distfiles
    193193--->  Attempting to fetch ircii-20020912.tar.gz from ftp://ircftp.au.eterna.com.au/pub/ircII/
    194194DEBUG: Executing com.apple.checksum (ircii)
     
    202202      <title>Verifying the Downloaded File</title>
    203203
    204       <para>Notice that DarwinPorts first checks for a local copy of
     204      <para>Notice that MacPorts first checks for a local copy of
    205205        <filename>ircii-20020912.tar.gz</filename> and doesn't find it,
    206206        so it then downloads from the remove site.  The port doesn't
     
    208208          statement in Portfile.</computeroutput>
    209209        Portfiles must contain an md5 checksum of all distribution
    210         files--this allows DarwinPorts to verify the accuracy and
     210        files--this allows MacPorts to verify the accuracy and
    211211        authenticity of the sources.  For convenience, an md5 checksum
    212212        of the downloaded files is printed when the
     
    243243--->  Extracting for ircii-20020912
    244244--->  Extracting ircii-20020912.tar.gz ... DEBUG: Assembled command: 'cd
    245 /Users/kevin/opendarwin/proj/darwinports/dports/irc/ircii/work &amp;&amp; gzip -dc /opt/local/var/db/dports/distfiles/ircii-20020912.tar.gz | tar -xf -'
     245/Users/kevin/opendarwin/proj/macports/mports/irc/ircii/work &amp;&amp; gzip -dc /opt/local/var/db/mports/distfiles/ircii-20020912.tar.gz | tar -xf -'
    246246Done</literallayout></computeroutput></para>
    247247    </sect2>
     
    253253        <filename>work</filename> directory in the Portfile
    254254        directory, we can configure the sources to compile with the
    255         desired options.  By default DarwinPorts assumes the software
     255        desired options.  By default MacPorts assumes the software
    256256        you're porting uses an autoconf <filename>configure</filename>
    257257        script and  will pass the <option>--prefix=${prefix}</option>
    258258        argument to <filename>configure</filename>, specifying that the
    259259        software should be installed in the directory tree used by
    260         DarwinPorts.</para>
     260        MacPorts.</para>
    261261
    262262      <para>ircII's standard set of options is fine for a base
     
    445445              combined with the <varname>extract.suffix</varname> (by
    446446              default <filename>${name}-${version}.tar.gz</filename>)
    447               by default, and is used by DarwinPorts to fetch the
     447              by default, and is used by MacPorts to fetch the
    448448              distribution file.  If the name of the file on the server
    449449              is not the same as <filename>${name}-${version}.tar.gz
     
    528528        uncommitted ports.  Edit your
    529529        <filename>sources.conf</filename> file and
    530         add:<userinput>file:///User/foo/dports-dev</userinput> (or
    531         wherever your local dport tree is). Place all your <filename>Portfiles</filename>
     530        add:<userinput>file:///User/foo/mports-dev</userinput> (or
     531        wherever your local mport tree is). Place all your <filename>Portfiles</filename>
    532532        inside their corresponding portdirs (reflecting the name
    533533        of the port), which should in turn be placed inside directories
     
    548548        good way to check that the port installs into the destroot and
    549549        not directly into the main prefix directory, or elsewhere in
    550         the system.  This should succeed up to the point darwinports
     550        the system.  This should succeed up to the point macports
    551551        attempts to copy the port from the destroot into the
    552         darwinports prefix. Once you are confident the port is
    553         correctly destrooted install the port into the darwinports
     552        macports prefix. Once you are confident the port is
     553        correctly destrooted install the port into the macports
    554554        prefix using root privileges. </para>
    555555     
     
    559559        install anything onto the system directly, most software that
    560560        uses autoconf should behave correctly automatically as
    561         darwinports sets DESTDIR by default. If files are directly
     561        macports sets DESTDIR by default. If files are directly
    562562        installed to the system they will not be registered and
    563563        packaging will fail. </para>
     
    580580      Using a chrooted version of the OS to install and test ports
    581581      makes this much easier, see the chroot
    582       <ulink url="http://darwinports.gene-hacker.net/docs/howto/chroot_10.2/index.html">
     582      <ulink url="http://macports.gene-hacker.net/docs/howto/chroot_10.2/index.html">
    583583      HOWTO</ulink> for more details on how to set up the chroot. </para>
    584584    </sect2>
     
    600600    <title>Where can I ask for advice?</title>
    601601
    602     <para>Either on the <email>darwinports@opendarwin.org</email>
    603       mailing list, or on the #darwinports channel on irc.freenode.net.
     602    <para>Either on the <email>macports-dev@lists.macosforge.org</email>
     603      mailing list, or on the #macports channel on irc.freenode.net.
    604604      Don't be afraid to ask questions! You should also look at the
    605605      later sections of the <link linkend="details">guide</link>and the
     
    676676
    677677    <para>For more examples, you can browse the directory tree of
    678       DarwinPorts' <filename>dports</filename> directory and have a look
     678      MacPorts' <filename>mports</filename> directory and have a look
    679679      at the <filename>Portfile</filename>s of your favorite
    680680      ports.</para>
  • trunk/doc/guide/xml/portfiles/style.xml

    r26302 r26404  
    3030               
    3131                <sect2>
    32                         <title>CVS ID tags</title>
    33                         <para>On the first line of the Portfile you should put a cvs
    34                         ID tag. This tag will be expanded by cvs when the Portfile is
     32                        <title>Subversion ID tags</title>
     33                        <para>On the first line of the Portfile you should put a svn
     34                        ID tag. This tag will be expanded by svn when the Portfile is
    3535                        committed and allows people to see at a glance details like
    3636                        who was the last person to commit to a port and when the last
  • trunk/doc/guide/xml/portfiles/variants.xml

    r26302 r26404  
    66        <sect1>
    77                <title>What are variants?</title>
    8                 <para>DarwinPorts allows multiple versions of a port to be specified in a single Portfile. For example, vim can be built with and without x11 support. Rather than duplicate the whole port and have vim-x11 vim-nox ports DarwinPorts supports "variants". </para>
     8                <para>MacPorts allows multiple versions of a port to be specified in a single Portfile. For example, vim can be built with and without x11 support. Rather than duplicate the whole port and have vim-x11 vim-nox ports MacPorts supports "variants". </para>
    99
    1010        </sect1>
  • trunk/doc/guide/xml/project/info.xml

    r26302 r26404  
    1010  </chapterinfo>
    1111 
    12   <title>DarwinPorts Project Info</title>
     12  <title>MacPorts Project Info</title>
    1313
    1414  <sect1>
    1515    <title>About this Chapter</title>
    1616
    17                 <para>This chapter contains basic information about the DarwinPorts
     17                <para>This chapter contains basic information about the MacPorts
    1818                project.</para>
    1919  </sect1>
     
    2121  <sect1>
    2222          <title>Mailing Lists</title>
    23           <para>The DarwinPorts project is organized through mailing lists,
     23          <para>The MacPorts project is organized through mailing lists,
    2424                and discussion on those lists ranges from new user help to bugs and
    25                 fixes to discussions about the future direction of DarwinPorts.
     25                fixes to discussions about the future direction of MacPorts.
    2626          </para>
    2727                <variablelist>
    28                         <varlistentry id='darwinports_at'>
     28                        <varlistentry id='macports_at'>
    2929                                <term><ulink
    30                                 url="http://www.opendarwin.org/mailman/listinfo/darwinports">darwinports
     30                                url="http://www.opendarwin.org/mailman/listinfo/macports">macports
    3131                                [at] opendarwin DOT org</ulink></term>
    3232                                <listitem>
    33                                         <para>General discussion about DarwinPorts development, new
     33                                        <para>General discussion about MacPorts development, new
    3434                                        user help, and most all discussion surrounding
    35                                         DarwinPorts.</para>
     35                                        MacPorts.</para>
    3636                                </listitem>
    3737                        </varlistentry>
    3838
    39                         <varlistentry id='darwinports_bugs_at'>
     39                        <varlistentry id='macports_bugs_at'>
    4040                                <term><ulink
    41                                 url="http://www.opendarwin.org/mailman/listinfo/darwinports-bugs">darwinports-bugs
     41                                url="http://www.opendarwin.org/mailman/listinfo/macports-bugs">macports-tickets
    4242                                [at] opendarwin DOT org</ulink></term>
    4343                                <listitem>
    44                                         <para>All bugs entered in Bugzilla at OpenDarwin.org for
    45                                                 DarwinPorts... very little real communication goes on on
    46                                                 this list, it is used for DarwinPorts developers to view
     44                                        <para>All bugs entered in Trac at macports.org for
     45                                                MacPorts... very little real communication goes on on
     46                                                this list, it is used for MacPorts developers to view
    4747                                                new bugs that are automatically assigned to this mailing
    4848                                                list.</para>
     
    5050                        </varlistentry>
    5151
    52                         <varlistentry id='cvs_darwinports_all_at'>
     52                        <varlistentry id='svn_macports_all_at'>
    5353                                <term><ulink
    54                                 url="http://www.opendarwin.org/mailman/listinfo/cvs-darwinports-all">cvs-darwinports-all
    55                                 [at] opendarwin DOT org</ulink></term>
     54                                url="http://www.opendarwin.org/mailman/listinfo/svn-macports-all">macports-changes
     55                                [at] lists DOT macosforge DOT org</ulink></term>
    5656                                <listitem>
    57                                         <para>CVS Commit messages are sent to this list, and
     57                                        <para>Subversion commit messages are sent to this list, and
    5858                                        occasionally there is some discussion about a commit.  This is
    59                                         mainly a list for DarwinPorts developers, however if you want
    60                                         to track changes to DarwinPorts, you can subscribe to this
     59                                        mainly a list for MacPorts developers, however if you want
     60                                        to track changes to MacPorts, you can subscribe to this
    6161                                        list.</para>
    6262                                </listitem>
     
    6464
    6565                        <varlistentry id='portmgr_at'>
    66                                 <term>portmgr [at] opendarwin DOT org</term>
     66                                <term>portmgr [at] lists DOT macosforge DOT org</term>
    6767                                <listitem>
    68                                         <para>This list is closed and is the home of the DarwinPorts
     68                                        <para>This list is closed and is the home of the MacPorts
    6969                                                PortMgr steering group.  If you have an issue that needs to
    7070                                                be brought to the attention of PortMgr, send a mail to this
     
    7676
    7777        <sect1>
    78                 <title>DarwinPorts PortMgr</title>
     78                <title>MacPorts PortMgr</title>
    7979
    80                 <para>The DarwinPorts PortMgr Group is primarily responsible for
    81                                 the administritive decision making of DarwinPorts. For
    82                                 example managing the DarwinPorts website, approving cvs accounts,
    83                                 maintaining the DarwinPorts mailing lists, and other
     80                <para>The MacPorts PortMgr Group is primarily responsible for
     81                                the administritive decision making of MacPorts. For
     82                                example managing the MacPorts website, approving svn accounts,
     83                                maintaining the MacPorts mailing lists, and other
    8484                                organizational functions. Send mail to portmgr [at]
    8585                                opendarwin DOT org to get in contact with it.</para>
     
    9090                        <itemizedlist>
    9191                                <listitem>
    92                                         <para><emphasis>Markus W. Weissmann</emphasis>, mww [at] opendarwin
     92                                        <para><emphasis>Markus W. Weissmann</emphasis>, mww [at] macports
    9393                                        DOT org</para>
    9494                                </listitem>
    9595
    9696                                <listitem>
    97                                         <para><emphasis>Juan M. Palacios</emphasis>, jmpp [at] opendarwin
    98                                         DOT org</para>
     97                                        <para><emphasis>Juan M. Palacios</emphasis>, jmpp [at] macports
     98                    DOT org</para>
    9999                                </listitem>
    100100
    101101                                <listitem>
    102                                         <para><emphasis>James D. Berry</emphasis>, jberry [at] opendarwin
     102                                        <para><emphasis>James D. Berry</emphasis>, jberry [at] macports
    103103                                        DOT org</para>
    104104                                </listitem>
  • trunk/doc/guide/xml/project/membership.xml

    r26302 r26404  
    1313                </keywordset>
    1414        </chapterinfo>
    15         <title>DarwinPorts membership</title>
     15        <title>MacPorts membership</title>
    1616        <sect1>
    17                 <title>Becoming a DarwinPorts committer</title>
     17                <title>Becoming a MacPorts committer</title>
    1818
    19                 <para>Becoming a member of the DarwinPorts project with commit access
    20                 to our CVS repository is pretty much a matter of involvement in any of
     19                <para>Becoming a member of the MacPorts project with commit access
     20                to our Subversion repository is pretty much a matter of involvement in any of
    2121                the areas of the project and the record you can establish thereof. We
    22                 encourage any developer and/or volunteer to apply for a CVS account
     22                encourage any developer and/or volunteer to apply for a Subversion account
    2323                if certain simple requirements are met:</para>
    2424
     
    2929                                </term>
    3030                                <listitem>
    31                                         <para>One key attribute of any DarwinPorts committer must be
     31                                        <para>One key attribute of any MacPorts committer must be
    3232                                        enthusiasm for the project, so therefore we appreciate applicants
    3333                                        who've shown their involvement through active participation
    34                                         on the <ulink url="http://opendarwin.org/mailman/listinfo/darwinports">main user list</ulink>,
     34                                        on the <ulink url="http://opendarwin.org/mailman/listinfo/macports">main user list</ulink>,
    3535                                        either through general user support and/or project roadmap discussion
    3636                                        and brainstorming.</para>
     
    4242                                </term>
    4343                                <listitem>
    44                                         <para>If applying for access to the "dports" section of the project,
     44                                        <para>If applying for access to the "mports" section of the project,
    4545                                        an established record as a maintainer of already existing ports is
    4646                                        preferable. This can be accomplished either through the inheritance
    47                                         of abandoned ports (those with the sole darwinports [at] opendarwin DOT org
     47                                        of abandoned ports (those with the sole nomaintainer [at] macports DOT org
    4848                                        maintainer address) or through writing your own from scratch. If instead
    4949                                        you plan to apply to any other area of the project, like "base" or "www", contributions
     
    5151                                        plan to help with are certainly a big plus. In all cases, submissions to
    5252                                        the project should be processed per the instructions detailed on the
    53                                         "<ulink url="/docs/ch15.html">DarwinPorts Submissions</ulink>" chapter.</para>
     53                                        "<ulink url="/docs/ch15.html">MacPorts Submissions</ulink>" chapter.</para>
    5454                                </listitem>
    5555                        </varlistentry>
     
    6161                steering committee explaining your contributions, how long you've been involved
    6262                with the project and why think you'd make a good committer. The sole purpose of
    63                 said forum is overseeing the general evolution of DarwinPorts, so it is where you
     63                said forum is overseeing the general evolution of MacPorts, so it is where you
    6464                should turn to for membership requests.</para>
    6565
    6666                <para>For a brief listing of the duties &amp; benefits resulting from holding
    67                 an OpenDarwin account, along with a short jump start on CVS primaries, read
     67                an OpenDarwin account, along with a short jump start on Subversion primaries, read
    6868                OpenDarwin's <ulink url="http://opendarwin.org/en/articles/committer_guide/ar01s02.html">Committer's Guide</ulink>
    69                 for account applicants. The DarwinPorts' specific <ulink url="http://wiki.opendarwin.org/index.php/Darwinports:New_committers_guide">New Committer's Guide</ulink>
     69                for account applicants. The MacPorts' specific <ulink url="http://wiki.opendarwin.org/index.php/Darwinports:New_committers_guide">New Committer's Guide</ulink>
    7070                is also a must read for new comers to become acquainted with our own procedures
    7171                and guidelines.</para>
  • trunk/doc/guide/xml/project/policies.xml

    r26302 r26404  
    1010  </chapterinfo>
    1111 
    12   <title>DarwinPorts Policies</title>
     12  <title>MacPorts Policies</title>
    1313
    1414  <sect1>
     
    1616
    1717                <para>This chapter contains policies and procedures, as well as
    18                 responsbilities for the DarwinPorts Project.</para>
     18                responsbilities for the MacPorts Project.</para>
    1919  </sect1>
    2020
     
    2222          <title>Port Maintenance Protocol</title>
    2323          <para>
    24                   DarwinPorts does not enforce exclusive write access to the maintainer
     24                  MacPorts does not enforce exclusive write access to the maintainer
    2525                  of a given Port, however it is normal practice to inform the maintainer
    2626                  before making any changes to a Port. Detailed procedures are described
     
    3737                          <listitem>
    3838                                  Write patch for the port that resolves the issue,
    39                                   and email maintainer or file a bug in Bugzilla,
     39                                  and email maintainer or file a bug in Trac,
    4040                                  appropriately assigned to the maintainer of the port. If
    4141                                  you can't write a patch, file a bug and ignore the
     
    5454                                  If the person suggesting the changes does not have
    5555                                  write-access to the repository, they should send an
    56                                   email to darwinports@opendarwin.org with a summary of the
    57                                   bug and a reference to a bugzilla bug.
     56                                  email to macports-dev@lists.macosforge.org with a summary of the
     57                                  bug and a reference to a Trac bug.
    5858                          </listitem>
    5959
     
    6565                  <orderedlist>
    6666                          <listitem>
    67                                   A mass update to darwinports which touches many ports
    68                                   (usually because of a change in the darwinports
     67                                  A mass update to macports which touches many ports
     68                                  (usually because of a change in the macports
    6969                                  infrastructure)
    7070                          </listitem>
     
    7676                          <listitem>
    7777                                  The port maintainer is not defined or is assigned to
    78                                   darwinports@opendarwin.org. Feel free to take over
     78                                  nomaintainer@macports.org. Feel free to take over
    7979                                  such ports!
    8080                          </listitem>
     
    9191                          Abandonment is defined as when a bug has not been acknowledged
    9292                          for more than 3 weeks after the bug was filed. If this occurs
    93                           a new bug should be filed in bugzilla against the port with
     93                          a new bug should be filed in Trac against the port with
    9494                          the subject: [Port Abandoned] and that port should reference
    9595                          the ignored bug.
     
    106106    <title>Committer's Category Responsibility List</title>
    107107
    108                 <para>DarwinPorts has at least one committer responsible for each
     108                <para>MacPorts has at least one committer responsible for each
    109109                category of ports (<filename>www</filename>,
    110110                <filename>textproc</filename>, etc).  This is a list of those
  • trunk/doc/guide/xml/project/roadmap.xml

    r26302 r26404  
    1010  </chapterinfo>
    1111 
    12   <title>DarwinPorts Roadmap</title>
     12  <title>MacPorts Roadmap</title>
    1313
    1414  <sect1>
    1515    <title>About this Chapter</title>
    1616
    17     <para>This is the DarwinPorts roadmap for future development.  This
     17    <para>This is the MacPorts roadmap for future development.  This
    1818      chapter will contain a verbose TODO list for the project, as well
    1919      as (once these goals are acheived) a place where new features
     
    2323
    2424  <sect1>
    25     <title>Remove cruft from DarwinPorts API</title>
     25    <title>Remove cruft from MacPorts API</title>
    2626
    27     <para>Most of the DarwinPorts API (<function>dportsearch</function>,
     27    <para>Most of the MacPorts API (<function>mportsearch</function>,
    2828      etc) is intended for use by external applications, such as Ports
    29       Manager and <command>port</command>(1).  However, the DarwinPorts
     29      Manager and <command>port</command>(1).  However, the MacPorts
    3030      "API" has grown organically, and there is a lot of cruft and clean
    3131      up that could be done. One piece of low hanging fruit would be to
    32       use Tcl namespaces to properly remove the DarwinPorts API from the
    33       global namespace, and only namespace export the dport*
     32      use Tcl namespaces to properly remove the MacPorts API from the
     33      global namespace, and only namespace export the mport*
    3434      procedures.</para>
    3535  </sect1>
  • trunk/doc/guide/xml/project/submission.xml

    r26302 r26404  
    1616                </keywordset>
    1717        </chapterinfo>
    18         <title>DarwinPorts submissions</title>
     18        <title>MacPorts submissions</title>
    1919        <sect1>
    2020                <title>Submitting a Port</title>
     
    2323                associated patches scripts, etc allows us to keep track of port
    2424                submissions, process them efficiently and get them submitted as
    25                 quickly as possible to our dports CVS tree. The following sections
     25                quickly as possible to our mports Subversion tree. The following sections
    2626                will describe the standard port submission procedures. </para>
    2727               
     
    2929                        <title>Where to submit</title>
    3030                       
    31                         <para> All ports should be submitted via the DarwinPorts
    32                         <ulink url="http://www.opendarwin.org/bugzilla/">bugzilla tool
     31                        <para> All ports should be submitted via the MacPorts
     32                        <ulink url="http://www.opendarwin.org/bugzilla/">Trac tool
    3333                        </ulink>. Your submission will be automatically emailled to the
    3434                        members of the
    35                         <ulink url="http://www.opendarwin.org/mailman/listinfo/darwinports-bugs/">
    36                         darwinports-bugs</ulink> mailing list. If you are uncertain about
     35                        <ulink url="http://www.opendarwin.org/mailman/listinfo/macports-tickets/">
     36                        macports-tickets</ulink> mailing list. If you are uncertain about
    3737                        any aspect of your port, you may also want to email it with your
    3838                        questions and the bug number to 
    39                         <ulink url="mailto:darwinports@opendarwin.org">DarwinPorts</ulink>
     39                        <ulink url="mailto:macports-dev@lists.macosforge.org">MacPorts</ulink>
    4040                        mailing list.</para>
    4141                       
    4242                        <para>If you are submitting a modification, or an update to an
    4343                        existing port, please assign the port to the current maintainer
    44                         in your bugzilla submission, so that the automatic email is
     44                        in your Trac submission, so that the automatic email is
    4545                        directed to the maintainer, who will be best suited to deal
    4646                        with your submission.</para>
     
    5353                <sect2>
    5454               
    55                         <title>Using bugzilla to submit a Port</title>
     55                        <title>Using Trac to submit a Port</title>
    5656                       
    5757                        <para>The following section describes in some more detail how to
    58                         use Bugzilla to submit your port.</para>
     58                        use Trac to submit your port.</para>
    5959                       
    6060                        <sect3>
     
    6767                                                </term>
    6868                                                <listitem>
    69                                                         <para>Make sure you select the DarwinPorts
     69                                                        <para>Make sure you select the MacPorts
    7070                                                        project.</para>
    7171
     
    7878                                                </term>
    7979                                                <listitem>
    80                                                         <para>Select "dports" as the component. </para>
     80                                                        <para>Select "mports" as the component. </para>
    8181
    8282                                                </listitem>
     
    232232                       
    233233                                <para>The following general points should also be borne in
    234                                 mind when submitting to bugzilla:
     234                                mind when submitting to Trac:
    235235                                        <simplelist type="vert">
    236236                                                <member>Small changes may be attached or included
     
    242242                                                <member>Currently attachments must be sent in
    243243                                                using the current bug number, remeber to query
    244                                                 bugzilla to find out the current bug number, select
     244                                                Trac to find out the current bug number, select
    245245                                                 that bug and use the 'Create a New Attachment'
    246246                                                 link.</member>
     
    268268                                        <member>diff -u oldfile oldfile.new > oldfile.diff</member>
    269269                                       
    270                                         <member>use bugzilla to submit your port UPDATE, assigning the bug to the corresponding port maintainer.</member>
     270                                        <member>use Trac to submit your port UPDATE, assigning the bug to the corresponding port maintainer.</member>
    271271                                       
    272272                                </simplelist></para>
    273273
    274                         <para>Or using cvs diff:
     274                        <para>Or using svn diff:
    275275                                <simplelist type="vert">
    276                                         <member>checkout the original source using cvs</member>
     276                                        <member>checkout the original source using svn</member>
    277277                                        <member>edit the files and save your changes</member>
    278                                         <member>cvs diff -u sourcefile > sourcefile.diff</member>
    279                                         <member>use bugzilla to submit your port UPDATE, assigning the bug to the corresponding port maintainer.</member>
     278                                        <member>svn diff sourcefile > sourcefile.diff</member>
     279                                        <member>use Trac to submit your port UPDATE, assigning the bug to the corresponding port maintainer.</member>
    280280                                </simplelist></para>
    281281
     
    289289
    290290                <para>If you instead plan to contribute to the project by making a submission
    291                 to any other of its areas, like the "base" section holding the DarwinPorts
     291                to any other of its areas, like the "base" section holding the MacPorts
    292292                sources themselves, the guidelines for such are very similar to those outlined
    293293                above. Just be sure to choose the correct component (be that "base", "doc",
    294                 "www" or any other) of the DarwinPorts product when creating the Bugzilla entry.</para>
     294                "www" or any other) of the MacPorts product when creating the Trac entry.</para>
    295295
    296296        </section1>
  • trunk/doc/guide/xml/user/dp_manager.xml

    r26302 r26404  
    2323  </chapterinfo>
    2424 
    25   <title>DarwinPorts Manager</title>
     25  <title>MacPorts Manager</title>
    2626 
    2727  <sect1>
    2828    <title>About this chapter</title>
    2929
    30     <para>This chapter provides an overview of the DarwinPorts Manager
     30    <para>This chapter provides an overview of the MacPorts Manager
    3131      application and how to use it as an alternative to the command-line
    32       tools for DarwinPorts.</para>
     32      tools for MacPorts.</para>
    3333
    3434  </sect1>
    3535       
    36   <sect1 id='darwinportsmanager'>
    37     <title>DarwinPorts Manager.app</title>
     36  <sect1 id='macportsmanager'>
     37    <title>MacPorts Manager.app</title>
    3838   
    39     <para>DarwinPorts Manager.app is a Cocoa GUI for the DarwinPorts
     39    <para>MacPorts Manager.app is a Cocoa GUI for the MacPorts
    4040      project.  It will allow users to browse through available ports and
    4141      their descriptions and to download, install, and uninstall the
    42       software.  DarwinPorts Manager.app is currently under development,
     42      software.  MacPorts Manager.app is currently under development,
    4343      and is based on the older Ports Manager.app.</para>
    4444
    4545    <para>We will be providing a binary installer (a '.pkg') file in
    46       the near future for DarwinPorts Manager.app.</para>
     46      the near future for MacPorts Manager.app.</para>
    4747  </sect1>
    4848</chapter>
  • trunk/doc/guide/xml/user/portimages.xml

    r26302 r26404  
    1111  </chapterinfo>
    1212 
    13   <title>DarwinPorts Port Images</title>
     13  <title>MacPorts Port Images</title>
    1414 
    1515  <sect1>
    1616    <title>About this chapter</title>
    1717
    18                 <para>This chapter provides an overview of the DarwinPorts Port
     18                <para>This chapter provides an overview of the MacPorts Port
    1919                        Image model of installing and using ports for users of
    20                         DarwinPorts.  A more complete overview of Port Images can be found
    21                         in the DarwinPorts Internals part of this Guide.</para>
     20                        MacPorts.  A more complete overview of Port Images can be found
     21                        in the MacPorts Internals part of this Guide.</para>
    2222  </sect1>
    2323       
     
    3232                        repository location and then create links, or aliases, from that
    3333                        repository location into the <varname>${prefix}</varname> from
    34                         where you can use the DarwinPorts ports.</para>
     34                        where you can use the MacPorts ports.</para>
    3535
    3636                <para>Port Images provide the ability to test new versions of a
     
    4343                <title>Port Image Activation</title>
    4444
    45                 <para>With Port Images in DarwinPorts, the port is installed as an
    46                         <emphasis>image</emphasis> to the DarwinPorts <emphasis>image
     45                <para>With Port Images in MacPorts, the port is installed as an
     46                        <emphasis>image</emphasis> to the MacPorts <emphasis>image
    4747                        repository</emphasis>.  This repository can be thought of as an
    4848                        library of ports that actually contains all of the files belonging
     
    5151                       
    5252                <para>Activation simply creates the links into the
    53                         <varname>${prefix}</varname> of DarwinPorts.  DarwinPorts manages
     53                        <varname>${prefix}</varname> of MacPorts.  MacPorts manages
    5454                        any conflicts between any ports that are activated, and will
    5555                        inform you if one port is attempting to link a file that already
    5656                        exists and belongs to another port.  You have the option to force
    57                         DarwinPorts to go ahead and activate the port in the event of a
    58                         conflict, and DarwinPorts will continue, moving the old file out
     57                        MacPorts to go ahead and activate the port in the event of a
     58                        conflict, and MacPorts will continue, moving the old file out
    5959                        of the way.</para>
    6060
    61                 <para>By default, DarwinPorts will go ahead and activate a port when
     61                <para>By default, MacPorts will go ahead and activate a port when
    6262                        you run <userinput>port install vim</userinput>.  Once a port is
    6363                        installed and activated, you can <emphasis>deactivate</emphasis>,
     
    7373                <title>Using Port Images</title>
    7474
    75                 <para>DarwinPorts uses Port Images by default now, so if you are
    76                         using a recent release of DarwinPorts, you are using Port Images!
     75                <para>MacPorts uses Port Images by default now, so if you are
     76                        using a recent release of MacPorts, you are using Port Images!
    7777                        Port Images will work transparently for users used to the old
    78                         installation model of DarwinPorts, as well as those familiar with
     78                        installation model of MacPorts, as well as those familiar with
    7979                        other port systems.  If you wish to use the advanced features that
    8080                        Port Images provide, namely activation and deactivation, the
  • trunk/doc/guide/xml/user/user.xml

    r26302 r26404  
    1919                </keywordset>
    2020        </chapterinfo>
    21         <title>Using DarwinPorts</title>
     21        <title>Using MacPorts</title>
    2222       
    2323       
     
    2626                 
    2727                <para>This document provides a short guide to the basics of the
    28                 DarwinPorts system. The first section provides a short description
     28                MacPorts system. The first section provides a short description
    2929                of the goals of the project and a brief comparison with other systems.
    30                 Subsequent sections describe how to get, install, and use DarwinPorts
     30                Subsequent sections describe how to get, install, and use MacPorts
    3131                on your own machines. </para>
    3232
     
    3535       
    3636       
    37         <sect1 id='about_dports'>
    38                 <title>About DarwinPorts</title>
    39                
    40                 <para>The aim of the DarwinPorts project is to develop a second-
     37        <sect1 id='about_mports'>
     38                <title>About MacPorts</title>
     39               
     40                <para>The aim of the MacPorts project is to develop a second-
    4141                generation system for the building, installation and management of
    42                 third party software. DarwinPorts is mainly developed on Mac OS X,
     42                third party software. MacPorts is mainly developed on Mac OS X,
    4343                however by design it is quite portable and is intended to work on
    4444                other UNIX-like systems, especially *BSD and hopefully Linux-based
     
    4646
    4747               
    48                 <para>DarwinPorts is probably best described by comparison:  It's sort
     48                <para>MacPorts is probably best described by comparison:  It's sort
    4949                of like the <ulink url='http://www.freebsd.org/ports'>FreeBSD ports
    5050                collection</ulink> or <ulink url='http://fink.sf.org/'>Fink</ulink>
    5151                in that it automates the process of building third party software for
    52                 Mac OS X and other operating systems.  DarwinPorts also tracks all
     52                Mac OS X and other operating systems.  MacPorts also tracks all
    5353                dependency information for a given piece of software. In other words,
    5454                it knows what it needs to build and install and in what order for the
    55                 piece of software you want to work properly. DarwinPorts knows how to
     55                piece of software you want to work properly. MacPorts knows how to
    5656                make, build and install the software to a specific location, meaning
    57                 that software installed via DarwinPorts doesn't simply scatter itself
     57                that software installed via MacPorts doesn't simply scatter itself
    5858                all over the system or require user knowledge of dependencies in what
    5959                order. </para>
     
    6565                where each software has a directory within a category (like mail or
    6666                graphics). That directory contains the information needed to build the
    67                 piece of software. DarwinPorts also uses a directory structure like this,
     67                piece of software. MacPorts also uses a directory structure like this,
    6868                although unlike FreeBSD ports the intention is to avoid requiring a
    6969                complete copy of the 'Ports Tree' on every user's machine.  The FreeBSD
     
    8282                *build* a given Open Source project.  A package management system relies
    8383                on similar dependency information, but is focused on safely installing
    84                 (and de-installing) software.   Before DarwinPorts, most systems did
    85                 both at once; DarwinPorts, however, is explicitly designed as a pure
     84                (and de-installing) software.   Before MacPorts, most systems did
     85                both at once; MacPorts, however, is explicitly designed as a pure
    8686                ports collection which can use various package management systems.
    8787                </para>
     
    9292                more complex than it looks at first glance and there's always room for
    9393                fresh approaches to the problem.  Which is what we have set out to do
    94                 with DarwinPorts. There are certainly other systems, some of which have
     94                with MacPorts. There are certainly other systems, some of which have
    9595                already been mentioned, which have made their own attempts at solving
    9696                this problem. There will likely be many more such systems in the future
     
    100100
    101101               
    102                 <para>DarwinPorts is mostly written in Tcl, with some components written
    103                 in C. Tcl was chosen to allow DarwinPorts to be readily embedded in other
     102                <para>MacPorts is mostly written in Tcl, with some components written
     103                in C. Tcl was chosen to allow MacPorts to be readily embedded in other
    104104                applications (e.g. a Cocoa GUI) and to allow flexible, but easy to read
    105105                Portfiles. </para>
    106106
    107107               
    108                 <para>Even though DarwinPorts is written in Tcl, users do not need to know
     108                <para>Even though MacPorts is written in Tcl, users do not need to know
    109109                Tcl in order to use the system or even to add new ports.  Port description
    110110                files, though they are actually full Tcl programs in their own right, are
     
    115115       
    116116        <sect1 id='setup'>
    117                 <title>Installing DarwinPorts</title>
     117                <title>Installing MacPorts</title>
    118118               
    119119                <sect2 id='prerequisites'>
    120120                        <title>What you need</title>
    121121                       
    122                         <para>DarwinPorts primary target platform is Mac OS X 10.4
     122                        <para>MacPorts primary target platforms are Mac OS X 10.4
    123123                        "Tiger" and Mac OS X 10.3 "Panther" (i. e. Darwin 8.x and 7.x).
    124124                        However,
    125                         DarwinPorts should still work on Mac OS X 10.2 "Jaguar", although
    126                         most ports are no longer tested on Jaguar. DarwinPorts is also
     125                        MacPorts should still work on Mac OS X 10.2 "Jaguar", although
     126                        most ports are no longer tested on Jaguar. MacPorts was previously
    127127                        known to work on various other operating systems such as FreeBSD,
    128                         NetBSD, OpenBSD, and various Linux distributions.  These
    129                         instructions should enable DarwinPorts to be installed on any of
    130                         these platforms.</para>
    131 
    132                         <para>To install and use DarwinPorts you must install the Developer
     128                        NetBSD, OpenBSD, and various Linux distributions, but the MacPorts
     129                        project is no longer supports them.</para>
     130
     131                        <para>To install and use MacPorts you must install the Developer
    133132                        tools (gcc, autoconf etc on other platforms, also known as the
    134133                        "Xcode tools" on Mac OS X 10.3 and 10.4.).
     
    139138                </sect2>
    140139               
    141                 <sect2 id='getting_dports'>
    142                         <title>Obtaining DarwinPorts</title>   
    143                        
    144                         <para>Currently there are basically two ways to obtain DarwinPorts.
     140                <sect2 id='getting_mports'>
     141                        <title>Obtaining MacPorts</title>       
     142                       
     143                        <para>Currently there are basically two ways to obtain MacPorts.
    145144                        Either download the sources as a tarball or get the binary
    146145                        installer via the downloadable disk image (both available in the
    147                         <ulink url='http://www.darwinports.org/downloads/'>download
     146                        <ulink url='http://www.macports.org/downloads/'>download
    148147                        section</ulink>). If you choose the binary installer, you can skip
    149148                        the next sections.</para>
     
    155154                        <para>If you want to very closely track the latest ports and use
    156155                        the latest experimental features of the port tool, you may want to
    157                         use cvs to check out the sources from our cvs repository.</para>
    158                 </sect2>
    159                
    160                 <sect2 id='install_dports'>
    161                         <title>Installing DarwinPorts from sources</title>
    162                        
    163                         <para>To install DarwinPorts execute the following commands from the
    164                         darwinports/base directory.  These commands assume that you checked
    165                         out the darwinports tree from CVS or downloaded and extracted the
     156                        use svn to check out the sources from our svn repository.</para>
     157                </sect2>
     158               
     159                <sect2 id='install_mports'>
     160                        <title>Installing MacPorts from sources</title>
     161                       
     162                        <para>To install MacPorts execute the following commands from the
     163                        macports/base directory.  These commands assume that you checked
     164                        out the macports tree from Subversion or downloaded and extracted the
    166165                        tarball in your home directory.  Modify
    167166                        the <userinput>cd</userinput> command appropriately if you did
    168167                        otherwise.
    169                         <programlisting><![CDATA[% cd ~/darwinports/base
     168                        <programlisting><![CDATA[% cd ~/macports/base
    170169% ./configure
    171170% make
    172171% sudo make install]]></programlisting>
    173172                        This will compile and install all the necessary software. In order
    174                         to install DarwinPorts on *BSD the default group-ownership must be
     173                        to install MacPorts on *BSD the default group-ownership must be
    175174                        passed to each make command: <userinput>make DSTGRP=wheel
    176175                        </userinput>.</para>
    177176                </sect2>
    178177
    179                 <sect2 id='configure_dports'>
    180                         <title>Configuring for DarwinPorts</title>
     178                <sect2 id='configure_mports'>
     179                        <title>Configuring for MacPorts</title>
    181180                       
    182181                        <para>It is no longer necessary to edit
    183182                        <filename>${prefix}/etc/ports/sources.conf</filename> after installing
    184                         DarwinPorts.  If you change the location of the
    185                         <filename>dports</filename> directory, which was in
    186                         <filename>~/darwinports/dports</filename> based on the above
     183                        MacPorts.  If you change the location of the
     184                        <filename>mports</filename> directory, which was in
     185                        <filename>~/macports/mports</filename> based on the above
    187186                        examples, then you will still need to edit
    188187                        <filename>${prefix}/etc/ports/sources.conf</filename> and modify the
    189                         <userinput>file:///Users/mike/darwinports/dports</userinput> line
     188                        <userinput>file:///Users/mike/macports/mports</userinput> line
    190189                        to reflect the new location.  To edit the file you must use a
    191190                        command line text editor like pico or vi. </para>
     
    197196                       
    198197                        <para>You should add /opt/local/bin (or wherever you chose to
    199                         install DarwinPorts) to your shell's path.</para>
     198                        install MacPorts) to your shell's path.</para>
    200199
    201200                        <para>If you are using Mac OS X 10.3 "Panther", Mac OS X 10.4 "Tiger"
     
    216215
    217216                        <para>Once you have got this far, you should have a working
    218                         installation of DarwinPorts, you have installed the 'port'
     217                        installation of MacPorts, you have installed the 'port'
    219218                        command (by default this installed as
    220219                        <filename>/opt/local/bin/port</filename>)
    221220                        and the libraries it needs (in
    222                         <filename>/opt/local/share/darwinports</filename>
    223                         and <filename>/Library/Tcl/darwinports1.0</filename> by
     221                        <filename>/opt/local/share/macports</filename>
     222                        and <filename>/Library/Tcl/macports1.0</filename> by
    224223                        default.)
    225224                        </para>
     
    228227                </sect2>
    229228
    230                 <sect2  id='updating_dports'>
    231                         <title>Updating DarwinPorts</title>
    232                        
    233                         <para>New ports are always being added to the DarwinPorts dports
     229                <sect2  id='updating_mports'>
     230                        <title>Updating MacPorts</title>
     231                       
     232                        <para>New ports are always being added to the MacPorts mports
    234233                        tree, you should regularly update your tree to get access to new
    235234                        ports, and (hopefully) improved versions of current ports.
    236                         Currently the simplest way you can update the dports tree is to use
     235                        Currently the simplest way you can update the mports tree is to use
    237236                        the selfupdate feature of port.
    238237                        To start a (rsync based) selfupdate, just issue
     
    250249                        <variablelist>
    251250                                <varlistentry>
    252                                         <term>Updating your DarwinPorts ports</term>
     251                                        <term>Updating your MacPorts ports</term>
    253252
    254253                                        <listitem>
    255254                                                <para>To get the latest Portfiles (the instructions for
    256255                                                        building ports), you need to update your
    257                                                         <filename>dports</filename> tree via
     256                                                        <filename>mports</filename> tree via
    258257                                                        <programlisting><![CDATA[%port sync]]></programlisting>
    259258                                                </para>
     
    263262
    264263                                <varlistentry>
    265                                         <term>Updating your DarwinPorts infrastructure</term>
    266 
    267                                         <listitem>
    268                                                 <para>To get the latest DarwinPorts infrastructure (or
     264                                        <term>Updating your MacPorts infrastructure</term>
     265
     266                                        <listitem>
     267                                                <para>To get the latest MacPorts infrastructure (or
    269268                                                        "base") for building ports, you need to update your
    270269                                                        <filename>base</filename> via
     
    279278       
    280279        <sect1>
    281                 <title>Using DarwinPorts</title>
     280                <title>Using MacPorts</title>
    282281               
    283282                <sect2 id='port'>
     
    286285                        <!--
    287286
    288                         <para>Using DarwinPorts is very straightforward, most of the time
     287                        <para>Using MacPorts is very straightforward, most of the time
    289288                        all you need to do is execute a single command to install a port.
    290289                        For example, if you want to install the text editor vile, you'd
     
    316315
    317316                        <para>Once the port has been installed, you may want to delete
    318                         all the intermediate files that DarwinPorts has created while
     317                        all the intermediate files that MacPorts has created while
    319318                        building the port, to do this you should enter:
    320319                        <userinput>port clean vile</userinput>.</para>
    321320                        -->
    322321
    323                         <para>Using the DarwinPorts <userinput>port</userinput> command is
     322                        <para>Using the MacPorts <userinput>port</userinput> command is
    324323                        very straight-forward.  Most of the time all you need to do is
    325324                        execute a single command to install a port.  For example, if you
     
    378377                                        <listitem>
    379378                                                <para>Once the port has been installed, you may want to
    380                                                 delete all the intermediate files that DarwinPorts has
     379                                                delete all the intermediate files that MacPorts has
    381380                                                created while building the port.  To do this, simply use the
    382381                                                <userinput>clean</userinput> option:</para>
     
    513512                        some reason. When this occurs you will get an error message
    514513                        like 'port search failed: expected integer but got "PortIndex"'.
    515                         You can fix problem by moving to the dports directory
    516                         (/Users/mike/darwinports/dports in our examples) and
     514                        You can fix problem by moving to the mports directory
     515                        (/Users/mike/macports/mports in our examples) and
    517516                        executing: <userinput>portindex</userinput>. This will go
    518                         through all the available ports in the dport directory and
     517                        through all the available ports in the mport directory and
    519518                        build an index file called PortIndex.</para>
    520519
     
    522521               
    523522       
    524                 <sect2 id='uninstall_dports'>
     523                <sect2 id='uninstall_mports'>
    525524                        <title>Removing ports</title>
    526525                       
     
    531530                </sect2>
    532531               
    533                 <sect2 id='upgrade_dports'>
     532                <sect2 id='upgrade_mports'>
    534533                        <title>Upgrading ports</title>
    535534                        <para>You can check if a port is outdated with the following command:
     
    568567                problem (details on how to <link linkend='user_bugs'>report problems</link>
    569568                 follow) check that the problem is described here, or in the
    570                  <ulink url='http://www.opendarwin.org/projects/darwinports/en/faq.php'>
     569                 <ulink url='http://www.opendarwin.org/projects/macports/en/faq.php'>
    571570                 FAQ</ulink> first.</para>
    572571
     
    603602                        <title>Bug reports</title>
    604603                        <para>If the you have updated your ports tree, searched the
    605                         darwinports@opendarwin.org mailling list archives and read the
     604                        macports-dev@lists.macosforge.org mailling list archives and read the
    606605                        common problems and the FAQ and you still can't find the answer
    607                         to the problem, you should submit a bug report via bugzilla.</para>
     606                        to the problem, you should submit a bug report via Trac.</para>
    608607
    609608
     
    620619                                                </term>
    621620                                                <listitem>
    622                                                         <para>Make sure you select the DarwinPorts
     621                                                        <para>Make sure you select the MacPorts
    623622                                                        project.</para>
    624623
     
    631630                                                </term>
    632631                                                <listitem>
    633                                                         <para>Select "dports" as the component. </para>
     632                                                        <para>Select "mports" as the component. </para>
    634633
    635634                                                </listitem>
Note: See TracChangeset for help on using the changeset viewer.