Haskell is a pure functional language. The Debian Haskell Group (DHG for friends!) is the team committed to packaging and maintaining a working and up-to-date Haskell environment and library in Debian.

Upstream references

• http://www.haskell.org/ -- Haskell main web site

• http://www.haskell.org/cabal/ -- Cabal (Common Architecture for Building Applications and Libraries), a program used to distribute many Haskell packages. Importing in Debian cabalized Haskell packages is quite an easy task, because most of the packaging and metadata writing work is already done. This is why we accept in Debian nearly only Cabal packages (nearly all Haskell packages are cabalized, though, so that's not a very restrictive decision).

• http://hackage.haskell.org/ -- Hackage, the main Haskell packages archive; nearly any Haskell package you can find is here.

Team contacts

• General discussion mailing list: http://lists.debian.org/debian-haskell/

• Maintainer and commit lists: https://alioth.debian.org/mail/?group_id=31040

• IRC: #debian-haskell

Team infrastructure

• Alioth Project: http://alioth.debian.org/projects/pkg-haskell -- to contribute to the DHG, register on Alioth and then use this link to ask for project membership; of course, you also need to subscribe to the mailing lists

• Package Entropy Tracker: http://pkg-haskell.alioth.debian.org/cgi-bin/pet.cgi -- this PET only shows packages that are team-maintained using darcs

• Dependency tree of our packages: http://pkg-haskell.alioth.debian.org/haskell-pkg-graph.pdf -- updated only manually; colors indicate installability

Other links

• Haskell Policy

• Status of Haskell platform in Debian

• Comparision of Version numbers in Debian and on Hackage

• Ubuntu wiki page

• Buildd status of our package with unsupported arches hidden, compact mode.

• permanent Haskell transition tracker

Haskell packaging

• /CollabMaint/Processes -- information on our group-internal processes

• ?/CollabMaint/PackageTemplate -- template for the package of a simple library.

All team-maintained packages are kept under some VCS (Version Control System). The most preferred is darcs (which is itself written in Haskell), other use git. Darcs has the advantage of being integrated with the Package Entropy Tracker, which makes it easier to check how things are going with Haskell package.

If you're using darcs:

• ?/CollabMaint/DarcsBasic -- instructions for using our Darcs repositories

If you're using git:

• ?/CollabMaint/GitBasic -- Use Git to check out code and submit commits

• ?/CollabMaint/GitPackaging -- instructions for using git-buildpackage to build from source

• ?/CollabMaint/GitCreation -- create new git repositories

TODO list

A raw list of things to do, hoping that somedays someone will start working on them...

• Fix policy, which is very old
  • Adapt it to the current best-practises and haskell-devscripts workflow

  • Description guidelines, see for example http://lists.debian.org/4C2FA27F.50303@poisson.phc.unipi.it

• Fix wiki pages, which are very old too (some examples are completely deprecated)
• Create some Lintian test specific for Haskell packages
• Include --datasubdir=$(DEB_CABAL_PACKAGE) in hlibrary.mk

• Libraries worth packaging: ?/PackageTODO

Relevant packages

• ?GHC is now being team maintained

Out-of-date things

This list is kept for historical interest. If you're interested how thing (should) go now, you're in the wrong place.

• A blog post about packaging Haskell

• Another (really old) example of how to package a Haskell library using dh_haskell