Hi,
at and after the DebConf talk we decided that we really should be
creating our Debian packaging more automatically, and we need a tool for
that. And cabal-debian is already such a tool! So we should use it.
Currently, it is not quite good enough; there are a few things that it
could or should be doing differently, or where best practices have
changed a litte (e.g. watch files). So I’d like to find out how best to
develop these changes.
David, I assume that you are using cabal-debian at Seereason, so you
might not want our changes without checking them. Do you have a
suggestion on how we should do this? Should we simply keep the
Debian-specific patches in debian/patches? Should we have a fork from
which you sync occasionally? Should we reverse it, i.e. we become the
primary maintainer, and you submit your patches (if any)?
Also, cabal-debian --help says things like
(This is an option whose use case is lost in the mists of time.)
We certainly do not use these things. Should we simply remove it and
clean it up a bit?
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
Attachment:
signature.asc
Description: This is a digitally signed message part