[27547] trunk/doc/guide/new/xml/portfiledev.xml

source_changes at macosforge.org source_changes at macosforge.org
Tue Aug 7 12:35:37 PDT 2007


Revision: 27547
          http://trac.macosforge.org/projects/macports/changeset/27547
Author:   markd at macports.org
Date:     2007-08-07 12:35:36 -0700 (Tue, 07 Aug 2007)

Log Message:
-----------
Portfile reference intro text tweaking.

Modified Paths:
--------------
    trunk/doc/guide/new/xml/portfiledev.xml

Modified: trunk/doc/guide/new/xml/portfiledev.xml
===================================================================
--- trunk/doc/guide/new/xml/portfiledev.xml	2007-08-07 19:01:47 UTC (rev 27546)
+++ trunk/doc/guide/new/xml/portfiledev.xml	2007-08-07 19:35:36 UTC (rev 27547)
@@ -13,11 +13,11 @@
 
     <para>Every MacPorts port has a corresponding
     <filename>Portfile</filename>, but Portfiles do not completely define a
-    port's behavior because the MacPorts base code sets the default behavior
-    for a port's installation phases. <filename>Portfiles</filename> may
-    contain optional section(s) of installation phase declarations, but they
-    are only necessary if you want to augment or override the default port
-    phase behavior defined in the MacPorts base.</para>
+    port's installation behavior because the MacPorts base code performs
+    default installation phases for all ports. However,
+    <filename>Portfiles</filename> may contain optional installation phase
+    declaration(s) to augment or override the default port phase behavior
+    performed by the MacPorts base during port installation.</para>
 
     <para>If you use phase declaration(s) in a <filename>Portfile</filename>,
     you should know how to identify what is called the "global" section of a
@@ -58,7 +58,7 @@
     </itemizedlist>
 
     <para>The default installation phase behavior performed by the MacPorts
-    base code is set for applications that use the standard
+    base by works fine for applications that use the standard
     <command>configure</command>, <command>make</command>, and <command>make
     install</command> steps, which conform to phases configure, build, and
     destroot respectively. For applications that do not conform to this

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20070807/908adfd9/attachment.html


More information about the macports-changes mailing list