[Hackage] #231: "buildable: False" should fail the current configuration

Hackage trac at galois.com
Mon Feb 4 20:15:22 EST 2008

#231: "buildable: False" should fail the current configuration
  Reporter:  duncan         |        Owner:         
      Type:  defect         |       Status:  new    
  Priority:  normal         |    Milestone:         
 Component:  Cabal library  |      Version:
  Severity:  normal         |     Keywords:         
Difficulty:  normal         |   Ghcversion:  6.8.2  
  Platform:                 |  
 Currently resolving configurations does not take account of the
 `buildable` field. It should act rather like `build-depends: non-
 existant`, though with a different error message.

 If possible the error message should relate to the guard condition
 expression (the conjunction if there are several nested guards).

 At the moment it is not considered at all and we don't notice that the
 package cannot be built until the build step, rather than the configure

 One problem is that it's not clear if `buildable: False` is always fatal.
 People sometimes do that for test executables that are not supposed to be
 installed. So what should the behaviour be? The lib or only exe failing to
 configure must be an error.

Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/231>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects

More information about the cabal-devel mailing list