[Hackage] #936: Add Haddock-Options field to Cabal package description

Hackage cvs-ghc at haskell.org
Tue Apr 3 23:26:31 CEST 2012

#936: Add Haddock-Options field to Cabal package description
  Reporter:  guest                |        Owner:            
      Type:  enhancement          |       Status:  new       
  Priority:  normal               |    Milestone:  Cabal-1.16
 Component:  Cabal specification  |      Version:  
  Severity:  normal               |     Keywords:            
Difficulty:  unknown              |   Ghcversion:            
  Platform:                       |  

Comment(by duncan):

 I think I see. So yes, it is a little like the current `default-
 extensions:` field which applies the extensions to all the modules in the
 package so you don't have to use LANGUAGE pragmas in each module. What I
 don't want is to have a general haddock-options field because most options
 are not applicable. Another alternative is to heavily restrict the allowed
 options, as we do for ghc, but a more explicit approach might be better.

 It's really a haddock global style thing, e.g. if haddock ever decided to
 allow markdown and that were enabled by a flag, that would be a similar
 one where it's the package author who decides.

Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/936#comment:5>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects

More information about the cabal-devel mailing list