Haskell related Debian packages

Simon Marlow simonmar@microsoft.com
Fri, 13 Dec 2002 09:23:40 -0000

> Please excuse me if anyone feels that this email isn't=20
> appropriate for this mailing list.  Though these are somewhat=20
> Debian-specific questions, I thought that some Haskell folks=20
> could lent their insight.  You would be the users after all.

Also see the recent discussion on glasgow-haskell-users about a library
building/packaging system (which didn't really reach a conclusion).

> There aren't many examples of libraries (without any=20
> binaries) that are packaged thus far.  I noticed that=20
> ctklight installs stuff in /usr/share/hugs98/extentions, but=20
> it can be used with GHC also, so I am not sure why its done=20
> this way. I don't use hugs too much though, also I don't know=20
> anything about nhc.
> So I'm considering sticking the *.lhs files for HUnit, for=20
> example, in /usr/share/hunit.  Then people can alter their=20
> Makefiles to include that directory in either hugs or ghc,=20
> but I see one problem with that: GHC would want to compile=20
> the source files, and stick them in /usr/share/hunit, but=20
> would be unable to (because of permissions problems when=20
> users compile).
> The package could install binary files, but then it would=20
> build-depend on ghc which doesn't exist for several Debian=20
> platforms.  So I guess it could check to see if ghc is=20
> installed on the building computer and stick binaries in /usr/lib.

I think I would have two versions of each package: one that builds &
installs a package for GHC, and one that installs source files for use
with Hugs (GHCi can use the GHC package).  These really are entirely
different beasts, and in most cases will have zero files in common, so I
think it makes sense to separate them altogether.

That way you don't have to require GHC in order to install the Hugs
version of the package, and vice-versa.