[34069] trunk/doc-new/guide/xml/portfiledev.xml
ryandesign at macports.org
ryandesign at macports.org
Mon Feb 11 13:17:03 PST 2008
Revision: 34069
http://trac.macosforge.org/projects/macports/changeset/34069
Author: ryandesign at macports.org
Date: 2008-02-11 13:17:02 -0800 (Mon, 11 Feb 2008)
Log Message:
-----------
minor wording / capitalization
Modified Paths:
--------------
trunk/doc-new/guide/xml/portfiledev.xml
Modified: trunk/doc-new/guide/xml/portfiledev.xml
===================================================================
--- trunk/doc-new/guide/xml/portfiledev.xml 2008-02-11 20:50:07 UTC (rev 34068)
+++ trunk/doc-new/guide/xml/portfiledev.xml 2008-02-11 21:17:02 UTC (rev 34069)
@@ -552,9 +552,9 @@
<listitem>
<para>Now you may place the patch
- <filename>patch-Makefile.in</filename> in location
+ <filename>patch-Makefile.in</filename> in the directory
<varname>${portpath}</varname>/files (either a local repository or
- after committing to the MacPorts subversion port repository) and use
+ after committing to the MacPorts Subversion port repository) and use
it in a port using the <code>patchfiles</code> keyword.</para>
<programlisting>patchfiles patch-Makefile.in</programlisting>
@@ -562,7 +562,7 @@
<note>
<para>You should create one patch file for each file to be
patched, though it is permissible to use existing patches you find
- that patch multiple files. Patchfiles filenames should generally
+ that patch multiple files. Patchfile filenames should generally
be of the form
<filename>patch-</filename><replaceable><directory></replaceable>-<replaceable><filename></replaceable>,
as shown in this example:
@@ -737,4 +737,4 @@
${name}-src-${version}</para>
</section>
</section>
-</chapter>
\ No newline at end of file
+</chapter>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20080211/a31566d2/attachment.html
More information about the macports-changes
mailing list