[Pkg-haskell-commits] darcs: policy: Fill in the package name hole and tidy up a bit

[Ian Lynagh]

Thu Jul 29 20:02:42 UTC 2004  Ian Lynagh <igloo at earth.li>
  * Fill in the package name hole and tidy up a bit

    M ./haskell-policy.sgml -14 +12

Thu Jul 29 20:02:42 UTC 2004  Ian Lynagh <igloo at earth.li>
  * Fill in the package name hole and tidy up a bit
diff -rN -u old-policy/haskell-policy.sgml new-policy/haskell-policy.sgml
--- old-policy/haskell-policy.sgml	2010-11-05 15:02:31.000988088 +0000
+++ new-policy/haskell-policy.sgml	2010-11-05 15:02:31.024989356 +0000
@@ -215,23 +215,21 @@
         </p>
 
         <p>
-            {XXX we need a mapping from cabal names to package names.
-            We (Debian) need a name matching (case sensitive)
-            [a-z0-9][-+.a-z0-9]+
-            If cabal uses [a-z0-9][-a-z0-9]* this is easy (id).
-            If cabal uses [a-zA-Z0-9][a-zA-Z0-9]* then perhaps
-            fooBar -&gt; foo-bar. Or foobar? What should FooBar map to?
-            If cabal allows both uppercase and - then what do we do?
-            Just lowercase everything and assume there won't be
-            collisions?
-            }
+            Cabal package names match the regex
+            <tt>[a-zA-Z][-a-zA-Z0-9]*</tt>, and the tools that
+            manipulate them are case preserving only.
+            For your package, calculate the <var>cname</var> from the
+            Cabal package name by converting all uppercase letters to
+            lowercase. If it is desirable for multiple versions of the
+            same cabal package to be installed at once on a Debian
+            system then you may append <tt>-<var>cversion</var></tt>,
+            where <var>cversion</var> is the cabal version.
         </p>
 
         <p>
-            If the name given by the above rules is <var>cname</var>
-            then the Debian source package should be called
+            The Debian source package &should; be called
             <tt>lib<var>cname</var></tt> and, for each implementation
-            <var>impl</var> that it is built for, it should make a
+            <var>impl</var> that it is built for, it &should; make a
             <tt>lib<var>impl</var>-<var>cname</var>-dev</tt> binary
             package.
         </p>
@@ -239,7 +237,7 @@
         <p>
             If multiple cabal packages are in a single upstream tarball,
             and repacking them separately does not seem sensible then
-            a sensible source package name should be chosen.
+            a suitable source package name should be chosen instead.
             A separate binary package for each cabal package, following
             the naming scheme above, &should; still be created.
         </p>