At Wed, 31 May 2006 10:30:14 -0700,
Isaac Jones wrote:
> 
> I haven't had a chance to look at this, but could you explain to the
> list what it does?  Like, we already have dh_haskell, does it use
> dh_haskell?  Is it a set of debian/ files that are suitable for
> Haskell libs?

I would describe it as a 'reference package' or 'best practices' for
using cabal + dh_haskell. In my experience, people are going to try to
cabalize+debianize a package by copying a pre-existing package. So I
figure we should provide a canonical reference package that "does it
right".

It contains the extra files you would need to take a non-cabalized,
non-debianized haskell library, and cabalize and debianize it. You
could use this either as a starting point for a library you are about
to write, or you could copy the parts you need in order to package a
pre-existing library.

The following sample files are provided:

./Makefile
./debian
./debian/control
./debian/rules
./debian/changelog
./debian/compat
./debian/haskell-package-doc.docs
./debian/copyright
./Setup.hs
./Package.cabal

I believe that in most cases you can adapt the sample files to a
specific haskell library using these steps (which are included in the
repository):

(1) Rename Package.cabal to YourPackage.cabal
(2) Edit YourPackage.cabal
(3) update debian/copyright
(4) edit debian/control and:
  (a) change occurances 'package' to 'yourpackage'
  (b) modify the 'Description' fields
  (c) add any extra Build-Depends
(5) edit debian/changelog

Documentation Generation Steps:

(6) Edit Makefile and change the 'doc' target as necessary - by
    default it just attempts to build Haddock documentation
(7) rename debian/haskell-package-doc.docs to
    debian/haskell-yourpackage-doc.docs
(8) edit the contents of haskell-yourpackage-doc.docs if neccessary

The above steps obviously assume you are familar with cabal and
debian.

j.

_______________________________________________
debian-haskell mailing list
[email protected]
http://urchin.earth.li/mailman/listinfo/debian-haskell

Reply via email to