Changeset 36879 for trunk/doc-new


Ignore:
Timestamp:
May 17, 2008, 4:08:50 AM (11 years ago)
Author:
markd@…
Message:

Improve some descriptions in the intro.

File:
1 edited

Legend:

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

    r34875 r36879  
    88    <title>Introduction</title>
    99
    10     <para>A MacPorts port has ten distinct phases. The MacPorts base is set to
    11     perform default steps for applications that use the standard
     10    <para>The MacPorts port installation process has a number of distinct
     11    phases that are described in detail in this section. The default scripts
     12    coded into MacPorts base performs the standard
    1213    <command>configure</command>, <command>make</command>, and <command>make
    13     install</command> steps, but for applications that do not conform to this
    14     behavior, installation phases may be declared in a Portfile to <link
     14    install</command> steps. For applications that do not conform to this
     15    standard, installation phases may be declared in a Portfile to <link
    1516    linkend="development.examples.augment">augment</link> or <link
    1617    linkend="development.examples.override">override</link> the default
     
    308309              <para>For ports that must fetch multiple download files from
    309310              different locations, you must label the files with tags and
    310               match the tags in a distfiles statement. The format is
    311               <literal>mirror:subdirectory:tag</literal>.</para>
     311              match the tags to a <literal>distfiles</literal> keyword. The
     312              format is <literal>mirror:subdirectory:tag</literal>.</para>
    312313
    313314              <para>In the example below, file_one.tar.gz is fetched from
     
    498499            <para>Change the fetch type. This is only necessary if a <link
    499500            linkend="reference.phases.fetch.cvs">CVS</link>, <link
    500             linkend="reference.phases.fetch.svn">svn</link>, or
    501             <link linkend="reference.phases.fetch.git">git</link> checkout is be
     501            linkend="reference.phases.fetch.svn">svn</link>, or <link
     502            linkend="reference.phases.fetch.git">git</link> checkout is be
    502503            used. <option>standard</option> is used for a normal http or ftp
    503504            fetch using <varname>${distfiles}</varname> and is used as
     
    782783      </variablelist>
    783784    </section>
    784    
     785
    785786    <section id="reference.phases.fetch.git">
    786787      <title>Fetch from Git</title>
    787788
    788       <para><ulink url="http://git.or.cz/">Git</ulink> may
    789       be used as an alternative method of fetching distribution files using
    790       the keywords in this section. However, fetching via Git may cause
    791       non-reproducible builds, so it is strongly discouraged.</para>
     789      <para><ulink url="http://git.or.cz/">Git</ulink> may be used as an
     790      alternative method of fetching distribution files using the keywords in
     791      this section. However, fetching via Git may cause non-reproducible
     792      builds, so it is strongly discouraged.</para>
    792793
    793794      <para>You have to set <link
     
    823824          <listitem>
    824825            <para>Optional tag for fetching with git, this specifies a branch
    825               (or other commit-ish) that git should checkout.
    826               Note that any branch besides HEAD should be prefixed by origin/.</para>
     826            (or other commit-ish) that git should checkout. Note that any
     827            branch besides HEAD should be prefixed by origin/.</para>
    827828
    828829            <itemizedlist>
     
    835836
    836837                <programlisting>git.branch             72bf1c8</programlisting>
     838
    837839                <programlisting>git.branch             origin/next</programlisting>
    838840              </listitem>
Note: See TracChangeset for help on using the changeset viewer.