Hi all,
I have a GHC tree that builds and uses haddock 6.10 during the build
process, and validates.
David, as I understand it you want to avoid having a separate haddock
repo for GHC, right? So currently what I've done is to make darcs-all
support absolute URLs in the packages file, e.g.:
utils/haddock http://code.haskell.org/haddock darcs
and push-all will not attempt to push to this repo (as the "remote path"
starts with "http:").
This puts haddock in a similar boat to Cabal, in that if you make
changes to it then you need to remember to push them specially.
Perhaps we should make push-all see if there are any local patches, and
shout loudly if there are?
This does mean that any patches to the main haddock repo need to pass
validate. Also, can we add some GHC people to the haddock group on
community?
Is this the best solution?
Another option would be to put both the HTTP and SSH URLs in packages,
but at that point I think we want to move to a more structured format.
Thanks
Ian
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
