Differences between revisions 28 and 29
Revision 28 as of 2011-07-25 19:03:32
Size: 4516
Editor: nomeata
Comment:
Revision 29 as of 2011-07-25 19:04:20
Size: 4520
Editor: nomeata
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
 * [[https://buildd.debian.org/status/package.php?p=pkg-haskell-maintainers%40lists.alioth.debian.org&suite=sid&compact=compact&a=amd64,armel,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,ppc,s390,sparc|Duildd status of our package]] with unsupported arches hidden, compact mode.  * [[https://buildd.debian.org/status/package.php?p=pkg-haskell-maintainers%40lists.alioth.debian.org&suite=sid&compact=compact&a=amd64,armel,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,s390,sparc|Duildd status of our package]] with unsupported arches hidden, compact mode.

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

Team infrastructure

Other links

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
  • 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.