Changeset 29303 for trunk/doc-new


Ignore:
Timestamp:
Sep 20, 2007, 8:06:02 PM (12 years ago)
Author:
dluke@…
Message:

Build the new guide from the doc-new directory (new guide no longer requires configure to be run in base, so the script is much simpler)

Location:
trunk/doc-new/guide/xml
Files:
4 edited

Legend:

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

    r29146 r29303  
    6060
    6161  <xi:include href="project.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
    62 
    63   <xi:include href="glossary.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
    6462</book>
  • trunk/doc-new/guide/xml/portfiledev.xml

    r29143 r29303  
    6767    destroot respectively. For applications that do not conform to this
    6868    standard behavior, any installation phase may be augmented using <link
    69     linkend="development.examples.augment">pre- and/or post- phases</link>, or
    70     even <link linkend="development.examples.override">overridden</link> or
     69    linkend="development.examples.pre-post">pre- and/or post- phases</link>,
     70    or even <link linkend="development.examples.override">overridden</link> or
    7171    <link linkend="development.examples.eliminate">eliminated</link>. See
    7272    <link linkend="development.examples">Example Portfiles</link>
     
    515515        <listitem>
    516516          <para>Now use the Unix command <command>diff -u </command>to create
    517           a "unified" diff patch file. Put the name of the port in the
    518           patchfile, for example, Portfile-rrdtool.diff.</para>
     517          a "unified" diff patch file. Name the patchfile
     518          appropriately.</para>
    519519
    520520          <programlisting><prompt>%%</prompt> <userinput>diff -u Portfile.orig Portfile &gt; Portfile-rrdtool.diff</userinput></programlisting>
     
    616616          <filename>patch-Makefile.in</filename> in the path ${portpath}/files
    617617          of a local repository (or commit it to subversion) and use it in a
    618           port using the <code>patchfiles</code> keyword.</para>
     618          port using the patchfiles keyword.</para>
    619619
    620620          <programlisting>patchfiles              patch-Makefile.in</programlisting>
    621 
    622           <note>
    623             <para>You should make a patch file for each file to be patched,
    624             though if you obtain a patch from another source that patches
    625             multiple files it is permissible to use it that way. Patch
    626             filenames should generally be of the form
    627             "patch-&lt;directory&gt;-&lt;filename&gt;", as shown in this
    628             example: <filename>patch-src-Makefile.in</filename>.</para>
    629           </note>
    630621        </listitem>
    631622      </orderedlist>
     
    636627
    637628      <para>Though MacPorts applies patch files automatically, you may want to
    638       know how to apply patch files manually if you want to test patch files
    639       you have created or you wish to apply uncommitted Portfile
    640       patches.</para>
     629      know how to apply patch files manually if you want to apply uncommitted
     630      Portfile patches or other similar uses.</para>
    641631
    642632      <orderedlist>
     
    653643          patchfile knows the filename of the file to be patched.</para>
    654644
    655           <programlisting><prompt>%%</prompt> <userinput>patch -p0 &lt; ~/Desktop/Portfile-postfix.diff</userinput></programlisting>
     645          <programlisting><prompt>%%</prompt> <userinput>patch &lt; ~/Desktop/Portfile.diff</userinput></programlisting>
    656646
    657647          <screen>patching file Portfile</screen>
     
    671661      <title>Don't Overwrite Config Files</title>
    672662
    673       <para>TODO:</para>
     663      <para></para>
    674664    </section>
    675665
     
    677667      <title>Install Docs and Examples</title>
    678668
    679       <para>TODO:</para>
     669      <para></para>
    680670    </section>
    681671
     
    683673      <title>Provide User Messages</title>
    684674
    685       <para>TODO:</para>
    686     </section>
    687 
    688     <section id="development.practices.use-variables">
    689       <title>Use Variables</title>
    690 
    691       <para>TODO: Set variables so changing paths may be done in one place;
    692       use them anytime it makes updates simpler: distname
    693       ${name}-src-${version}</para>
     675      <para></para>
    694676    </section>
    695677  </section>
  • trunk/doc-new/guide/xml/portfileref.xml

    r29143 r29303  
    1717    install</command> steps, but for applications that do not conform to this
    1818    behavior, installation phases may be declared in a Portfile to <link
    19     linkend="development.examples.augment">augment</link> or <link
     19    linkend="development.examples.pre-post">augment</link> or <link
    2020    linkend="development.examples.override">override</link> the default
    2121    behavior as described in the <link linkend="development">Portfile
  • trunk/doc-new/guide/xml/using.xml

    r29168 r29303  
    4343DEBUG: Synchronizing ports tree(s)
    4444Synchronizing from rsync://rsync.macports.org/release/ports/
    45 DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/ports/
     45DEBUG: /usr/bin/rsync -rtzv rsync://rsync.macports.org/release/ports/
    4646receiving file list ... done
    4747
Note: See TracChangeset for help on using the changeset viewer.