Changeset 1102 for trunk/doc


Ignore:
Timestamp:
Oct 20, 2002, 4:59:57 AM (17 years ago)
Author:
michaelm
Message:

more guide files

Location:
trunk/doc/guide/xml
Files:
7 added
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/guide/xml/quick.xml

    r977 r1102  
    11<?xml version="1.0" encoding="iso-8859-1" ?>
    2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
     2<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
    33                "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
    44
    5 <chapter>
     5<chapter id="quickstart">
     6        <chapterinfo>
     7                <keywordset>
     8                        <keyword>portfile</keyword>
     9                        <keyword>introduction</keyword>
     10                        <keyword>maintainer</keyword>
     11                </keywordset>
     12        </chapterinfo>
    613    <title>Quick Start</title>
    714    <sect1>
     
    1219            Portfile and then explain the syntax that is used. </para>
    1320    </sect1>
    14     <sect2>
     21    <sect1>
    1522        <title>Basic Portfile</title>
    1623        <para> This is the first example (A real Portfile doesn't have the line numbers, they are
    1724            used for clarity in the explanation only). </para>
    18         <sect3>
     25        <sect2>
    1926            <title> Example Portfile 1</title>
    20             <example label="expat-portfile">
     27            <example>
     28                <title>Expat Portfile</title>
    2129                <programlisting><![CDATA[
    2230########################### expat Portfile ##################################
     
    6472                    <listitem>
    6573                        <para> Each port must have at least one category and may have more than one.
    66                             The primary category should be listed first. </para>
     74                            The primary category should be listed first. (The primary category is
     75                            also the directory under which the port is stored). </para>
    6776                    </listitem>
    6877                </varlistentry>
     
    138147                </varlistentry>
    139148            </variablelist>
    140         </sect3>
    141         <sect3>
    142             <title> Example Portfile 2></title>
     149        </sect2>
     150        <sect2>
     151            <title> Example Portfile 2</title>
    143152            <para> A second example Portfile will give you an idea of how to deal with slightly more
    144153                complicated ports. </para>
    145             <example label="neon-portfile">
     154            <example>   
     155                <title>Neon Portfile</title>
    146156                <programlisting><![CDATA[
    147157###########################neon Portfile####################################
     
    16017013> configure.env LDFLAGS=-L$prefix/lib CPPFLAGS=-I$prefix/include
    16117114> configure.args --with-ssl \
    162 15> --with-force-ssl \ 1
    163 6> --enable-xml \
     17215> --with-force-ssl \
     17316> --enable-xml \
    16417417> --enable-shared \
    16517518> --with-expat
     
    224234                </varlistentry>
    225235            </variablelist>
    226         </sect3>
    227     </sect2>
    228     <sect2>
     236        </sect2>
     237    </sect1>
     238
     239        <sect1>
    229240        <title>Common Mistakes</title>
    230         <sect3>
     241        <sect2>
    231242            <title>Don't quote or wrap items in '{}'.</title>
    232243            <para> Frequently people submit ports with the description or configure arguments
     
    235246                wrapped in curly brackets because of the very large number of files some ports
    236247                install make escaping all the newlines extremely irritating. </para>
    237         </sect3>
    238     </sect2>
     248        </sect2>
     249    </sect1>
    239250    <sect1>
    240251        <title>How to test</title>
Note: See TracChangeset for help on using the changeset viewer.