Update of /cvsroot/fink/web/xml/packaging
In directory sc8-pr-cvs5.sourceforge.net:/tmp/cvs-serv30156

Modified Files:
        packaging.en.xml 
Log Message:
Document InfoTest.


Index: packaging.en.xml
===================================================================
RCS file: /cvsroot/fink/web/xml/packaging/packaging.en.xml,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -d -r1.87 -r1.88
--- packaging.en.xml    22 Feb 2006 06:31:55 -0000      1.87
+++ packaging.en.xml    18 Sep 2006 14:34:38 -0000      1.88
@@ -1443,7 +1443,10 @@
 <p>In the <em>compile phase</em> the source is configured and
 compiled. Usually this means calling the <code>configure</code> script
 with some parameters and then issuing a <code>make</code> command. See the
-CompileScript field description for details.</p>
+CompileScript field description for details.  If test suites are enabled
+for the build (a new feature in fink 0.25, currently achieved by building in
+maintainer mode), the TestScript will be run immediately after the
+CompileScript.</p>
 <p>In the <em>install phase</em> the package is installed to a temporary
 directory, <filename>/sw/src/fink.build/root-gimp-1.2.1-1</filename> (= %d). 
(Note the "root-" part.)
 All files that would normally be installed to <filename>/sw</filename> are 
installed in
@@ -1869,7 +1872,9 @@
 A list of dependencies that is applied at build time only.
 This can be used to list tools (e.g. flex) that must be present to
 build the packages, but which are not used at run time.
-Supports the same syntax as Depends.
+Supports the same syntax as Depends.  If a build is being done
+with test suites enabled, the dependencies in the <code>TestDepends</code>
+field will be added to this list.
 </p>
 </itemd></item>
 
@@ -1921,7 +1926,9 @@
 being compiled. This can be used to prevent <code>./configure</code>
 or the compiler from seeing undesired library headers or to avoid use
 of a version of a tool that is known to be broken (for example, a bug
-in a certain version of sed).
+in a certain version of sed).  If a build is being done
+with test suites enabled, the packages in the <code>TestConflicts</code>
+field will be added to this list.
 </p>
 </itemd></item>
 
@@ -2056,6 +2063,10 @@
 download).
 This implicitly-defined <code>Source</code> form is deprecated
 (explicitly-stated simple filename/manual download is still okay).
+</p><p>
+Sources that are only needed in order to run test suites should
+use <code>TestSource</code> and related fields, inside the
+<code>InfoTest</code> block.
 </p>
 </itemd></item>
 
@@ -2421,7 +2432,9 @@
 <itemd>
 <p>
 Additional parameters to pass to the configure script. (See
-CompileScript for details.)
+CompileScript for details.)  If a build is being done
+with test suites enabled, the value of the <code>TestConfigureParams</code>
+field will be appended to this.
 
 As of fink > 0.13.7, this parameter will also work with perl modules
 <code>Type: Perl</code>, and will append to the default perl Makefile.PL
@@ -2553,6 +2566,46 @@
 </itemd></item>
 
 </itemtable>
+<p><em>Test Suites:</em></p>
+<itemtable>
+
+<item><itemt>InfoTest</itemt>
+<itemd>
+<p>
+<em>Introduced in fink 0.25.</em>
+This field encapsulates information that will only be used when performing
+a build with test suites enabled.  It contains other fields.
+If present, this field <em>must</em> contain a <code>TestScript</code>.
+All other fields are optional.  The following fields are allowed inside
+<code>InfoTest</code>:
+</p><ul>
+<li><code>TestScript</code>: A script which runs the test suite.  This script 
should exit
+    with status 0 if the suite passes, 1 to indicate warnings, or any other
+    value to indicate failures serious enough to be considered fatal.
+    Because of this tri-state logic, you should explicitly set an exit value in
+    this script.  For instance, <code>make check</code> is a bad script,
+    since it will exit with status 1 if the check target doesn't exist.
+    <code>make check || exit 2</code> would be a better script.</li>
+<li><code>TestConfigureParams</code>: A value which will be appended to 
<code>ConfigureParams</code>.</li>
+<li><code>TestDepends</code> and <code>TestConflicts</code>: Lists of packages 
that will be added to the <code>BuildDepends</code> or 
<code>BuildConflicts</code> lists.</li>
+<li><code>TestSource</code>: Extra sources necessary to run the test suite.  
All of the
+    affiliated fields are also supported, so you <em>must</em> also specify
+    <code>TestSource-MD5</code>, and you may also have
+    <code>TestSourceN</code> and corresponding <code>TestSourceN-MD5</code>,
+    <code>TestTarFilesRename</code>, etc.</li>
+<li><code>TestSuiteSize</code>: Describes approximately how long the test 
suite takes to
+    run.  Valid values are <code>small</code>, <code>medium</code>, and 
<code>large</code>.
+    This field is currently ignored.</li>
+<li>Any other standard field.  If a field is specified both inside and outside
+<code>InfoTest</code>, the value inside <code>InfoTest</code> will replace
+the other value when test suites are active.</li>
+</ul><p>Here's an example:
+</p><codeblock>InfoTest: &lt;&lt;
+    TestScript: make check || exit 2
+    TestConfigureParams: --enable-tests
+&lt;&lt;</codeblock>
+</itemd></item>
+</itemtable>
 <p><em>Install Phase:</em></p>
 <itemtable>
 


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Fink-commits mailing list
Fink-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-commits

Reply via email to