[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packaging my first haskell package



Dear Andreas,

thanks for your interest in Haskell.

Am Dienstag, den 08.12.2015, 14:24 +0100 schrieb Andreas Tille:
> I need to dive into Haskell packaging from scratch since there was a
> request of a Debian Med user to package PhyBin[1].  I started with
> cabal-debian which created a basic packaging dir which I changed to some
> extend.  I pushed my results to the Debian Med packaging Git[2] which is
> writable to any DD (so feel free to commit patches there if this
> simplifies things).

It looks as if you created this with an old(ish) version of cabal-
debian...

Anyways, in general we heavily advocate against Haskell library
packages being maintained outside the Haskell group. The
interdependencies between packages are intricate and it is just so much
less hassle if you can work on them all at once. In fact, we even have
all of them in one git repository.

Now in your packaging, you build both the library and the binary
packages. Are you sure the library packages are of importance? Often in
such cases, only the binary package (phybin) is useful for Debian, and
not having the library packages greatly simplifies things.

Also, the upstream package has not seen an upload in over two years.
For hackage packages, this is often a sign of insufficent upstream
activity, which can cause the package to cause problems for us, and
eventually a swift removal. Are you sure this is an actively maintained
project?

If so, we’d have a lot less to worry if it were part of stackage
(which, in a way, is a Distribution-independent distribution of Haskell
package). I suggest you contact the author and talk him into adding his
package to stackage, which is easy and provides free QA to him:
http://www.stackage.org/authors

If you really need the library (and not just the binary), I suggest
that the Debian Haskell Team takes it over.

> I also need to add that I intend to backport the package to Jessie which
> might add some extra effort since I noticed that one of the dependencies
> (libghc-prettyclass-*) is not available in Jessie and besides this it is
> quite tricky to install a mix of Haskell packages from Jessie and
> Jessie-backports.

Right. That’s why we generally shun away from backporting of anything
more than simply GHC and cabal-install.

> I'm also aware that libghc-hierarchical-clustering-* is not even
> available in unstable but cabal-debian has added this to the
> Build-Depends.  I guess I need to package this as well.

Right; or even better, the DHG has to. That package looks more actively
maintained, but should also enter stackage before it gets into Debian.

> However, my main problem is currently that the template does not even
> build if I uncomment the currently missing Build-Depends and I'm running
> into
>
> ...
> The following packages have unmet dependencies:
> 

We (well, Clint) are currently in the progress of moving ~700 Haskell
packages from experimental to unstable, and we more or less
accidentally interleaved this with an upgrade of a few package, so
expect Haskell to be broken in unstable for a few more days.

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


Reply to: