On 10 October 2011 00:30, Duncan Coutts <duncan.cou...@googlemail.com> wrote: > Ok, all committed now except for one of the cabal-install patches.
Thanks! > I've not yet applied the cabal-install patch that makes the haddock > options available via cabal install. I'm not sure about making them > available directly as install commands since it's not clear from context > what e.g. cabal install --css means, plus we're likely to get name > clashes. I'll have a think about alternative approaches. OK, how about the attached approach, where haddock options are prefixed with "haddock-"? To address Ross's points, I also added a variable-substituted "haddock" command flag that allows us to pass the --use-contents flag to the haddock invocation. My changes to the documentation build client that make use of these changes will land in the hackage-server repo when I get access to my code.haskell.org account again and I can exercise my commit bit :-) Max
HaddockOptions.dpatch
Description: Binary data
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
