Changeset 27224 for trunk/doc


Ignore:
Timestamp:
Jul 25, 2007, 6:02:58 AM (12 years ago)
Author:
markd@…
Message:

Fix some missed markup.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/guide/new/xml/portfiledev.xml

    r27222 r27224  
    356356    <command>diff</command> that are applied using the command
    357357    <command>patch</command> to modify text files to fix bugs or extend
    358     functionality. </para>
     358    functionality.</para>
    359359
    360360    <section>
    361361      <title>Portfile Patches</title>
    362362
    363       <para>If you wish to contribute modifications or fixes to a Portfile,
    364       you should do so in the form of a patch.</para>
     363      <para>If you wish to contribute modifications or fixes to a
     364      <filename>Portfile</filename>, you should do so in the form of a
     365      patch.</para>
    365366
    366367      <orderedlist>
    367368        <listitem>
    368           <para>Make a copy of the Portfile you wish to modify. Both the
    369           Portfile and its copy must be in the same directory, though it may
    370           be any directory.</para>
     369          <para>Make a copy of the <filename>Portfile</filename> you wish to
     370          modify; both files must be in the same directory, though it may be
     371          any directory.</para>
    371372
    372373          <programlisting><prompt>%%</prompt> <userinput>cp Portfile Portfile.org</userinput></programlisting>
     
    379380
    380381        <listitem>
    381           <para>Now use the Unix command diff to create a "unified" diff patch
    382           file.</para>
     382          <para>Now use the Unix command <command>diff</command> to create a
     383          "unified" diff patch file.</para>
    383384
    384385          <programlisting><prompt>%%</prompt> <userinput>diff -u Portfile.org Portfile &gt; Portfile.diff</userinput></programlisting>
     
    386387      </orderedlist>
    387388
    388       <para>Now you may attach the Portfile.diff to a MacPorts Trac ticket for
    389       the port author to evaluate.</para>
     389      <para>Now you may attach the <filename>Portfile.diff</filename> to a
     390      MacPorts Trac ticket for the port author to evaluate.</para>
    390391    </section>
    391392
     
    414415
    415416        <listitem>
    416           <para>Now use the Unix command diff to create a "unified" diff patch
    417           file.</para>
     417          <para>Now use the Unix command <command>diff</command> to create a
     418          "unified" diff patch file.</para>
    418419
    419420          <programlisting><prompt>%%</prompt> <userinput>cd foo-1.34</userinput>
     
    421422
    422423          <note>
    423             <para>You must execute the diff command in the top-level of the
    424             unpacked source code. Otherwise the patch command will look for
    425             the file to be patched in the wrong place and fail.</para>
     424            <para>You must execute the <command>diff</command> command in the
     425            top-level of the unpacked source code. Otherwise the
     426            <command>patch</command> command will look for the file to be
     427            patched in the wrong place and fail.</para>
    426428          </note>
    427429        </listitem>
     
    430432          <para>A patch made using "-u" ("unified") is the easiest to
    431433          interpret by humans and this type should always be used for ports.
    432           See the example below where a patch file adds DESTDIR support to a
    433           <filename>Makefile.in</filename> file.</para>
     434          See the example below where a patch adds <varname>DESTDIR</varname>
     435          support to a <filename>Makefile.in</filename> file.</para>
    434436
    435437          <programlisting>--- Makefile.in.org   2007-06-01 16:30:47.000000000 -0700
     
    447449
    448450        <listitem>
    449           <para>Now you may use the patch file
    450           <filename>patch-Makefile.in</filename> in a port using the
    451           patchfiles keyword.</para>
     451          <para>Now you may place the patch
     452          <filename>patch-Makefile.in</filename> in the path ${portpath}/files
     453          of a local repository (or commit it to subversion) and use it in a
     454          port using the patchfiles keyword.</para>
    452455
    453456          <programlisting>patchfiles              patch-Makefile.in</programlisting>
Note: See TracChangeset for help on using the changeset viewer.