I use the cabal-debian library in a bunch of private packages. Also, for complicated debianizations there is a function in Debian.Debianize.Output called "runDebianizeScript" that actually runs the command "runhaskell debian/Debianize.hs", and that script definitely requires the cabal-debian library to run.You can see an example of a debian/Debianize.hs script here: https://github.com/clckwrks/clckwrks-dot-com/blob/master/debian/Debianize.hsOn Fri, Jan 9, 2015 at 3:27 AM, Joachim Breitner <nomeata@debian.org> wrote:Hi,
Am Freitag, den 09.01.2015, 13:55 +0300 schrieb Dmitry Bogatov:
> * David Fox <ddssff@gmail.com> [2015-01-08 06:20:34-0800]
> > Also, cabal-debian should be producing library debs, if it isn't there may
> > be a bug.
>
> Seems I was not clear enough. I regret, that haskell-cabal-debian
> *debian* source package provides only *cabal-debian* binary, without
> *libghc-cabal-debian-dev*. I am working on fixing it.
do we really need libghc-cabal-debian-dev? What other package is using
it?
Note that uploading Haskell library packages comes at a cost, e.g.
testing migrations become larger, so we should only package libraries
that have actual uses.
Lots of Haskell programs define libraries in their .cabal file, but
these are only meant to be used by the executable therein.
Greetings,
Joachim
--
Joachim "nomeata" Breitner
Debian Developer
nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata