Changeset 913 for trunk/www


Ignore:
Timestamp:
Oct 4, 2002, 1:58:30 AM (18 years ago)
Author:
kevin
Message:

fixed the last xhtml bugs

Location:
trunk/www
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/www/en/portfileHOWTO.php

    r912 r913  
    33//
    44// File     : portfileHOWTO.php
    5 // Version  : $Id: portfileHOWTO.php,v 1.2 2002/10/04 01:48:58 kevin Exp $
     5// Version  : $Id: portfileHOWTO.php,v 1.3 2002/10/04 01:58:30 kevin Exp $
    66// Location : /projects/darwinports/portfileHOWTO.php
    77//
     
    127127<pre><tt>
    128128% port extract
    129 </pre></tt>
     129</tt></pre>
    130130<p>
    131131Which should display the following output:
     
    159159<a name="build"></a>Building the Sources
    160160</h3>
     161<p>
    161162To build, type the following:
    162163</p>
     
    166167<p>
    167168By default, the build phase executes the makefile using GNU make.  (This can be changed with the <tt>make/build.type</tt> option.)  The above step has starting compiling the sources, when it finishes we'll be ready to install the software. 
    168 
     169</p>
    169170
    170171<h3>
    171172<a name="install"></a>Installing the Finished Product on the System
    172173</h3>
     174<p>
    173175Portfiles are required to have a <tt>contents</tt> option which specifies which files are installed.  DarwinPorts uses this information to catalog what files belong to which piece of software so they may be later uninstalled.  Each parameter to <tt>contents</tt> is a path to a file.  All paths are relative to the <tt>${prefix}</tt> variable.  As a convenient way to determine exactly what files are installed as part of ircII, let's use the find command to compose a manifest of the files in the <tt>${prefix}</tt> tree.  After installing we'll re-run the find command, and use the differences to generate our contents list.
    174176</p>
     
    188190<p>
    189191Now that we have a contents file in our port directory, we should edit it to begin with <tt>contents {</tt> and end with a closing <tt>}</tt>.  (It is important to note that any other process using the <tt>${prefix}</tt> tree may interfere with the accuracy of the <tt>find</tt> command.  You should audit the resulting <tt>contents</tt> file to look for any files that appear out of place, specifically some DarwinPorts temporary files such as <tt>/var/db/dports/receipts/ircii-20020912.tmp</tt>.)  Next we should edit the Portfile to include our contents file:
     192</p>
    190193<pre><tt>
    191194include contents
  • trunk/www/portfileHOWTO.php

    r912 r913  
    33//
    44// File     : portfileHOWTO.php
    5 // Version  : $Id: portfileHOWTO.php,v 1.2 2002/10/04 01:48:58 kevin Exp $
     5// Version  : $Id: portfileHOWTO.php,v 1.3 2002/10/04 01:58:30 kevin Exp $
    66// Location : /projects/darwinports/portfileHOWTO.php
    77//
     
    127127<pre><tt>
    128128% port extract
    129 </pre></tt>
     129</tt></pre>
    130130<p>
    131131Which should display the following output:
     
    159159<a name="build"></a>Building the Sources
    160160</h3>
     161<p>
    161162To build, type the following:
    162163</p>
     
    166167<p>
    167168By default, the build phase executes the makefile using GNU make.  (This can be changed with the <tt>make/build.type</tt> option.)  The above step has starting compiling the sources, when it finishes we'll be ready to install the software. 
    168 
     169</p>
    169170
    170171<h3>
    171172<a name="install"></a>Installing the Finished Product on the System
    172173</h3>
     174<p>
    173175Portfiles are required to have a <tt>contents</tt> option which specifies which files are installed.  DarwinPorts uses this information to catalog what files belong to which piece of software so they may be later uninstalled.  Each parameter to <tt>contents</tt> is a path to a file.  All paths are relative to the <tt>${prefix}</tt> variable.  As a convenient way to determine exactly what files are installed as part of ircII, let's use the find command to compose a manifest of the files in the <tt>${prefix}</tt> tree.  After installing we'll re-run the find command, and use the differences to generate our contents list.
    174176</p>
     
    188190<p>
    189191Now that we have a contents file in our port directory, we should edit it to begin with <tt>contents {</tt> and end with a closing <tt>}</tt>.  (It is important to note that any other process using the <tt>${prefix}</tt> tree may interfere with the accuracy of the <tt>find</tt> command.  You should audit the resulting <tt>contents</tt> file to look for any files that appear out of place, specifically some DarwinPorts temporary files such as <tt>/var/db/dports/receipts/ircii-20020912.tmp</tt>.)  Next we should edit the Portfile to include our contents file:
     192</p>
    190193<pre><tt>
    191194include contents
Note: See TracChangeset for help on using the changeset viewer.