On Tue, Jun 10, 2008 at 3:48 AM, Ian Lynagh <[EMAIL PROTECTED]> wrote:
> > Hi David, > > On Mon, Jun 09, 2008 at 03:23:31PM -0700, David Fox wrote: > > I have been working on the library documentation, specificially > debianizing > > haddock 2.1.0, getting everything in the Debian repository to build with > > haddock 2.1.0 > > Have you seen this thread: > http://www.haskell.org/pipermail/cvs-ghc/2008-June/042772.html > which continues here: > http://www.haskell.org/pipermail/cvs-libraries/2008-June/008910.html > ? In short, you may have to jump through hoops when upgrading to a new > version of GHC. Yes, I see the issue - by the second stage of the ghc build the haddock version becomes incompatible. Presumably haddock will have to be merged into the ghc package, or a way of relaxing haddock's version requirement will have to be added. Or you could modify the ghc debianization so it keeps the documentation it produced during stage 1, then you could rebuild haddock after the ghc build finished. However, since fiddling with #ifdef __HADDOCK__ was taking more and more of our time, and not having a fully integrated documentation tree was becoming more and more of an inconvenience, I thought it would be worth it to go ahead and upgrade. When you are ready to upgrade the official repositories I hope this code will be helpful. Actually, it may be that if you always pass -B /usr/lib/ghc* to haddock during the ghc build (rather than -B `$(HC) --print-libdeb` which would give you the library directory of the new, incompatible compiler) you should make it through the build. It seems like there is probably an easy workaround for this. Maybe I'll give it a try.
_______________________________________________ debian-haskell mailing list [email protected] http://urchin.earth.li/mailman/listinfo/debian-haskell
