[82429] trunk/doc-new/guide/xml/macports.conf.xml

[jmr at macports.org]

Revision: 82429
          http://trac.macports.org/changeset/82429
Author:   jmr at macports.org
Date:     2011-08-13 14:39:25 -0700 (Sat, 13 Aug 2011)
Log Message:
-----------
guide: update config files section

Modified Paths:
--------------
    trunk/doc-new/guide/xml/macports.conf.xml

Modified: trunk/doc-new/guide/xml/macports.conf.xml
===================================================================
--- trunk/doc-new/guide/xml/macports.conf.xml	2011-08-13 17:30:05 UTC (rev 82428)
+++ trunk/doc-new/guide/xml/macports.conf.xml	2011-08-13 21:39:25 UTC (rev 82429)
@@ -4,9 +4,10 @@
 <section id="internals.configuration-files">
   <title>Configuration Files</title>
 
-  <para>The MacPorts configuration files do not need to be modified for the
+  <para>The MacPorts configuration files often do not need to be modified for the
   general end user. They contain options that may be of use to advanced users
-  and port developers.</para>
+  and port developers. Some automatically configured options may need to be
+  updated when migrating to a new CPU architecture or a new OS version.</para>
 
   <para>There are three MacPorts configuration files that define important
   variables used by the MacPorts system: <filename>macports.conf</filename>,
@@ -83,28 +84,12 @@
         <term>portdbformat</term>
 
         <listitem>
-          <para>Storage type to use for the MacPorts registry: flat or sqlite.
-          Preferred format is sqlite, flat is legacy.</para>
+          <para>Formerly selected the storage type to use for the MacPorts registry: flat or sqlite.
+          Currently, only sqlite can be used.</para>
 
           <para>Default: <option>sqlite</option></para>
         </listitem>
       </varlistentry>
-
-      <varlistentry>
-        <term>portinstalltype</term>
-
-        <listitem>
-          <para>Sets the mode in which ports are installed by MacPorts.
-          Supported values are "direct" or "image". In "direct" mode ports are
-          installed directly into "${prefix}" and only one version of a port
-          can be installed at any given time. In "image" mode multiple
-          versions (and any possible combination of its variants) can be
-          installed concurrently into "${portdbpath}/software/${portname}" and
-          only one can be "activated" (hardlinked) into "${prefix}".</para>
-
-          <para>Default: <option>image</option></para>
-        </listitem>
-      </varlistentry>
       
       <varlistentry>
         <term>build_arch</term>
@@ -114,7 +99,7 @@
           Options include: ppc, i386, ppc64, x86_64</para>
 
           <para>Default: </para>
-          <para>(Snow Leopard) <option>x86_64</option> or <option>i386</option> depending on hardware</para>
+          <para>(Snow Leopard and later) <option>x86_64</option> or <option>i386</option> depending on hardware</para>
           <para>(Leopard/Tiger) <option>i386</option> or <option>ppc</option> depending on hardware</para>
         </listitem>
       </varlistentry>
@@ -145,7 +130,7 @@
         <term>developer_dir</term>
 
         <listitem>
-          <para>Directory where Xcode Tools is installed.</para>
+          <para>Directory where Xcode is installed.</para>
 
           <para>Default:
           <filename>/Developer</filename></para>
@@ -153,42 +138,14 @@
       </varlistentry>
 
       <varlistentry>
-        <term>portarchivemode</term>
-
-        <listitem>
-          <para>Create and use binary archive packages for
-          installation/reinstallation ease.</para>
-
-          <para>Default: <option>no</option></para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term>portarchivepath</term>
-
-        <listitem>
-          <para>Where to store/retrieve port binary archive files.</para>
-
-          <para>Default:
-          <filename>${prefix}/var/macports/packages</filename></para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
         <term>portarchivetype</term>
 
         <listitem>
-          <para>Type of binary archive packages to create when using archive
-          mode. Available types are: tgz, tar, tbz, tbz2, tlz, xar, zip, cpgz,
+          <para>Type of archive to use for port images.
+          Available types are: tgz, tar, tbz, tbz2, tlz, xar, zip, cpgz,
           cpio.</para>
 
-          <para>Multiple types are supported to build multiple file types in
-          one step. Unarchive uses multiple types as a search list to locate
-          an archive, and the first to match a specified type is used.
-          Multiple types must be separated by a colon or comma (NO
-          spaces).</para>
-
-          <para>Default: <filename>.tgz</filename></para>
+          <para>Default: <filename>tbz2</filename></para>
         </listitem>
       </varlistentry>
 
@@ -276,7 +233,7 @@
           <para>Rsync directory from which to pull the base/ component
           (infrastructure) of MacPorts.</para>
 
-          <para>Default: <filename>release/base/</filename></para>
+          <para>Default: <filename>release/tarballs/base.tar</filename></para>
         </listitem>
       </varlistentry>
 
@@ -401,7 +358,7 @@
     selfupdate</command> or <command>port sync</command> are run.</para>
 
     <para>Default:
-    <filename>rsync://rsync.macports.org/release/ports/</filename></para>
+    <filename>rsync://rsync.macports.org/release/tarballs/ports.tar [default]</filename></para>
 
     <para>Optional local repositories are enabled using a file url:
     <replaceable>file:///path/to/localportsrepository</replaceable></para>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20110813/6f7b49c2/attachment-0001.html>