[Pkg-haskell-commits] darcs: policy: Compiler deps and markup fixup
Ian Lynagh
igloo at earth.li
Fri Nov 5 15:02:52 UTC 2010
Sun Sep 5 22:49:36 UTC 2004 Ian Lynagh <igloo at earth.li>
* Compiler deps and markup fixup
M ./haskell-policy.sgml -12 +24
Sun Sep 5 22:49:36 UTC 2004 Ian Lynagh <igloo at earth.li>
* Compiler deps and markup fixup
diff -rN -u old-policy/haskell-policy.sgml new-policy/haskell-policy.sgml
--- old-policy/haskell-policy.sgml 2010-11-05 15:02:52.550126808 +0000
+++ new-policy/haskell-policy.sgml 2010-11-05 15:02:52.558127231 +0000
@@ -1,6 +1,6 @@
<!doctype debiandoc public "-//DebianDoc//DTD DebianDoc//EN"
[
-<!entity version "0.1.4">
+<!entity version "0.1.5">
<!entity must "<em>must</em>">
<!entity mustnot "<em>must not</em>">
<!entity should "<em>should</em>">
@@ -284,6 +284,18 @@
</p>
<p>
+ For simplicity's sake we will use this dependency scheme for
+ all Haskell implementations. As almost all libraries are
+ expected to be compiled for GHC this should not affect when
+ recompilation is necessary. All Haskell implementations
+ &must; provide a file
+ <file>/usr/lib/compiler/debian-dependencies</file>
+ that contains how the library must depend on the compiler,
+ e.g.
+ <tt>ghc6 (>= 6.2.1), ghc6 (<< 6.2.1+)</tt>.
+ </p>
+
+ <p>
The possibility of compiling libraries at install time was
considered, but was rejected due to its fragility and due to
it being against the spirit of Debian being a binary
@@ -304,21 +316,21 @@
Although there is no technical reason why all libraries need
be in the same place, in order to make life easier for users
all libraries &should; be installed into
- <filename>/usr/lib/haskell-libraries/compiler/package/</filename>
- where <filename>compiler</filename> is the source package
+ <file>/usr/lib/haskell-libraries/compiler/package/</file>
+ where <file>compiler</file> is the source package
name of the compiler they are to be used with.
</p>
<p>
- For each cabal package <filename>cp</filename>, a manual
- page <filename>cp.3haskell</filename> describing the purpose
+ For each cabal package <var>cp</var>, a manual
+ page <file><var>cp</var>.3haskell</file> describing the purpose
of the package and the list of modules it includes &should;
- be installed into <filename>/usr/share/man/man3</filename>.
+ be installed into <file>/usr/share/man/man3</file>.
Additionally, for each module
- <filename>Hierarchial.Module</filename>, a manual page
- <filename>cp.Hierarchial.Module.3haskell</filename>
+ <var>Hierarchial.Module</var>, a manual page
+ <file><var>cp</var>.<var>Hierarchial.Module</var>.3haskell</file>
dsecribing the purpose and interface of the module &should;
- be installed into <filename>/usr/share/man/man3</filename>.
+ be installed into <file>/usr/share/man/man3</file>.
XXX We'd like to mention haddock here, but it can't output
manual pages yet, can it?
</p>
@@ -326,7 +338,7 @@
<p>
Additionally, you &should; provide documentation in other
formats such as, but not limited to, plain text and HTML in
- <filename>/usr/share/doc/package</filename>. It is expected
+ <file>/usr/share/doc/package</file>. It is expected
that most libraries will provide documentation in the form
accepted by haddock, making this easy.
</p>
@@ -348,8 +360,8 @@
<p>
As normal, each executable should install a Manual page with
- the extension <filename>.1</filename> into
- <filename>/usr/share/man/man1</filename>.
+ the extension <file>.1</file> into
+ <file>/usr/share/man/man1</file>.
</p>
</chapt>
More information about the Pkg-haskell-commits
mailing list