On Tuesday 05 October 2004 6:40 pm, Isaac Jones wrote: > On Tue, 05 Oct 2004 13:08:42 -0500, John Goerzen <[EMAIL PROTECTED]> wrote: > > Package: wnpp > > Severity: wishlist > > > > * Package name : haskell-cabal > > I think I would prefer to maintain this package, if you don't mind.
No problem. I just wanted to make sure it is in sid. I have made uploads already for the source package that generates a binary package for ghc6. I have added all the hooks necessary for it to build ghc5 and also fixed some places in the source where it was incompatible with ghc5, but there is a bug relating to subdirectories in the ./setup build support for ghc5 that prevents that build from working. Also, I fixed postinst and prerm, modified the packages to put the libraries in the locations mandated by the Debian haskell policy (or as close as possible, at least), modified the build-deps and deps for same, added copyright text, etc. nhc98 support should also be fairly easily added, and Hugs too if the source is compatible with it. So let me know when you want to take it over. If the answer is "now", please contact me for my diff.gz. (Actually, you'll probably want it anyway, since you probably want to commit those ghc5 fixes to your source tree at least). But I've got some more Debian stuff to contribute yet. If you (or someone) can fix the ghc5 issue, then we'll get at least a ghc5 lib out of it. > I'm not sure it's ready to enter Debian yet... the interface isn't > finalized, so I'd like to keep it out of testing. So far, it is likely to be used only as a Build-Dep in Debian, which means it's an internal problem for us to sort out (not bothering end users). But if it is kept out of testing, then there goes MissingH, Hunit, and HSQL -- unless those are all converted to using something else like hmake, which seems like a waste of time since the world is standardizing on Cabal. Interfaces have changed before. We can handle it. > BTW, there's a tool for creating a skeleton Debian package from a > cabal-ized package. See debianTemplate and dh_make. I saw that, though my .debs aren't building with it yet. I'm concerned that some of the files it is using (especially postinst/prerm) are buggy. I also wanted to wait until I have a generic infrastructure for building a library with all four compilers/interpreters in Debian first, then patch the template to support that. I'm close, but haven't tested it yet since I don't yet have any code that actually builds with all four compilers/interpreters in Debian... But I hope to have that all done in a day or two, time permitting. -- John
