Hi Claus, > my suggestion: > - keep it as a separate repo, but let darcs-all fetch it > - build haddock.ghc during ghc's make, but distribute > it as a separate tool > > that way, it would get daily builds and, more importantly, > anyone making a change that affects haddock.ghc would > notice that instantly, and could update it.
I think its likely that if someone makes a change that effects haddock.ghc, then David is the person to fix it up. What I think is more useful is nightly builds, and that isn't just useful for haddock.ghc, its useful for Yhc, Hugs and everything on hackage! Perhaps rather than shove another tool into the GHC tool chain, perhaps someone can setup buildbots in a way that we can easily add projects to the list? Thanks Neil _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
