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

[source_changes at macosforge.org]

Revision: 27832
          http://trac.macosforge.org/projects/macports/changeset/27832
Author:   markd at macports.org
Date:     2007-08-14 17:52:20 -0700 (Tue, 14 Aug 2007)

Log Message:
-----------
Add a section for manually applying patches to the Patch Files section.

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-15 00:28:32 UTC (rev 27831)
+++ trunk/doc/guide/new/xml/portfiledev.xml	2007-08-15 00:52:20 UTC (rev 27832)
@@ -437,7 +437,7 @@
   </section>
 
   <section>
-    <title>Creating Patch Files</title>
+    <title>Patch Files</title>
 
     <para>Patch files are files created with the Unix command
     <command>diff</command> that are applied using the command
@@ -445,7 +445,7 @@
     functionality.</para>
 
     <section>
-      <title>Portfile Patches</title>
+      <title>Creating Portfile Patches</title>
 
       <para>If you wish to contribute modifications or fixes to a
       <filename>Portfile</filename>, you should do so in the form of a
@@ -507,7 +507,7 @@
     </section>
 
     <section>
-      <title>Source Code Patches</title>
+      <title>Creating Source Code Patches</title>
 
       <para>Necessary or useful patches to application source code should be
       sent to the application developer (not the port author) so the
@@ -573,5 +573,32 @@
         </listitem>
       </orderedlist>
     </section>
+
+    <section>
+      <title>Manually Applying Patches</title>
+
+      <para>Though MacPorts applies patch files automatically, you may want to
+      know how to apply patch files manually if you want to apply uncommitted
+      Portfile patches or other similar uses.</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Change to the directory containing the file to be patched. In
+          this example, we'll apply a <filename>Portfile</filename> patch to
+          the postfix port.</para>
+
+          <programlisting><prompt>%%</prompt> <userinput>cd /opt/local/var/macports/sources/rsync.macports.org/release/ports/mail/postfix</userinput></programlisting>
+        </listitem>
+
+        <listitem>
+          <para>Now apply the patch that is on the current user's desktop. The
+          patchfile knows the filename of the file to be patched.</para>
+
+          <programlisting><prompt>%%</prompt> <userinput>patch &lt; ~/Desktop/Portfile.diff</userinput></programlisting>
+
+          <screen>patching file Portfile</screen>
+        </listitem>
+      </orderedlist>
+    </section>
   </section>
 </chapter>
\ No newline at end of file

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