[29143] trunk/doc/guide/new/xml

source_changes at macosforge.org source_changes at macosforge.org
Sat Sep 15 13:50:13 PDT 2007


Revision: 29143
          http://trac.macosforge.org/projects/macports/changeset/29143
Author:   markd at macports.org
Date:     2007-09-15 13:50:12 -0700 (Sat, 15 Sep 2007)

Log Message:
-----------
Corrections submitted by simon@

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

Modified: trunk/doc/guide/new/xml/portfiledev.xml
===================================================================
--- trunk/doc/guide/new/xml/portfiledev.xml	2007-09-15 19:34:57 UTC (rev 29142)
+++ trunk/doc/guide/new/xml/portfiledev.xml	2007-09-15 20:50:12 UTC (rev 29143)
@@ -66,8 +66,8 @@
     install</command> steps, which conform to phases configure, build, and
     destroot respectively. For applications that do not conform to this
     standard behavior, any installation phase may be augmented using <link
-    linkend="development.examples.pre-post">pre- and/or post- phases</link>,
-    or even <link linkend="development.examples.override">overridden</link> or
+    linkend="development.examples.augment">pre- and/or post- phases</link>, or
+    even <link linkend="development.examples.override">overridden</link> or
     <link linkend="development.examples.eliminate">eliminated</link>. See
     <link linkend="development.examples">Example Portfiles</link>
     below.</para>
@@ -685,7 +685,7 @@
       <para>TODO:</para>
     </section>
 
-    <section>
+    <section id="development.practices.use-variables">
       <title>Use Variables</title>
 
       <para>TODO: Set variables so changing paths may be done in one place;

Modified: trunk/doc/guide/new/xml/portfileref.xml
===================================================================
--- trunk/doc/guide/new/xml/portfileref.xml	2007-09-15 19:34:57 UTC (rev 29142)
+++ trunk/doc/guide/new/xml/portfileref.xml	2007-09-15 20:50:12 UTC (rev 29143)
@@ -16,7 +16,7 @@
     <command>configure</command>, <command>make</command>, and <command>make
     install</command> steps, but for applications that do not conform to this
     behavior, installation phases may be declared in a Portfile to <link
-    linkend="development.examples.pre-post">augment</link> or <link
+    linkend="development.examples.augment">augment</link> or <link
     linkend="development.examples.override">override</link> the default
     behavior as described in the <link linkend="development">Portfile
     Development</link> chapter.</para>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20070915/616ee358/attachment.html


More information about the macports-changes mailing list