[Pkg-haskell-commits] darcs: policy: Small tidyups and testsuite

[Ian Lynagh]

Sun Sep  5 21:21:26 UTC 2004  Ian Lynagh <igloo at earth.li>
  * Small tidyups and testsuite

    M ./haskell-policy.sgml -4 +21

Sun Sep  5 21:21:26 UTC 2004  Ian Lynagh <igloo at earth.li>
  * Small tidyups and testsuite
diff -rN -u old-policy/haskell-policy.sgml new-policy/haskell-policy.sgml
--- old-policy/haskell-policy.sgml	2010-11-05 15:02:35.749238999 +0000
+++ new-policy/haskell-policy.sgml	2010-11-05 15:02:35.757239422 +0000
@@ -1,6 +1,6 @@
 <!doctype debiandoc public "-//DebianDoc//DTD DebianDoc//EN"
 [
-<!entity version "0.1.1">
+<!entity version "0.1.2">
 <!entity must      "<em>must</em>">
 <!entity mustnot   "<em>must not</em>">
 <!entity should    "<em>should</em>">
@@ -232,7 +232,7 @@
             <tt>lib<var>cname</var></tt> and, for each implementation
             <tt><var>impl</var></tt> that it is built for, it &should; make a
             <tt>lib<var>impl</var>-<var>cname</var>-dev</tt> binary
-            package.
+            package. XXX this needs more thought.
         </p>
 
         <p>
@@ -248,9 +248,9 @@
             optimisations, such as inlining.  This means that even small
             internal changes to a library <tt><var>foo</var></tt> can
             cause programs that link with a library
-            <tt><var>bar</var></tt> which links uses
+            <tt><var>bar</var></tt> which, in turn, uses
             <tt><var>foo</var></tt> to fail to link, or even to link
-            successfully but give incorrect results.  Therefore
+            successfully but give incorrect results. Therefore
             libraries &must; depend on the exact version of other
             Haskell libraries that they were compiled against.
             Furthermore, they must build-depend on the exact version of
@@ -315,6 +315,23 @@
             prefering those that produce better code.
         </p>
     </chapt>
+
+    <chapt id="testsuites">
+        <heading>Testsuites</heading>
+        <p>
+            For both libraries and programs you &should;, in the source
+            package, include a pair of shell scripts
+            <file>debian/haskell-testsuite-inplace</file> and
+            <file>debian/haskell-testsuite-installed</file>. If these
+            exist they &must; run a testsuite, using the library or
+            program in the build tree or from the installed package
+            respectively. The build dependencies &must; be sufficient to
+            run the testsuites. The testsuites &mustnot; be interactive.
+            The inplace testsuite &should; be run as part of the package
+            build; normally, if the testsuite fails the build should
+            also fail.
+        </p>
+    </chapt>
 </book>
 </debiandoc>