Hi, if you have followed the recent discussion on the Haskell library and cafe list, you might have noticed that there is a reluctancy in the Haskell community to stop creating packages for tiny fragments of code. Eventually, this will not scale any more for us. The solution that we could work towards (after the migration, the earliest) is to bundle related Cabal packages into one source package, but still create multiple binary package. The rought roadmap would be * Use the dpkg quilt 3.0 multi upstream tarball feature. * As there is no standard: Think about how to store the list of versions of the bundled tarballs in the source package, e.g. debian/source/versions. * Wait for bugs.debian.org/531321 to be fixed or replace our use of uscan --download by, say, debian/rules get-orig-tarball * Modify haskell-devscript to be able to build more than one Cabal package, even when one depends on the other (Is doable, after all the ghc package does it). * Either hard-code the order of building or, better, include some code that figures it out. I see uses for it for example for the Haskell-Platform, for the hxt series of packages, for the leksah packages, for the gtk2hs package, for the various sets of database packages – basically for every set of packages that are usually updated in lockstep anyways. Might be an interesting task for a DebCamp. But first, the transition... Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part