[Hackage] #592: cabal test does not detect that cabal build needs to be re-run

[Hackage]

#592: cabal test does not detect that cabal build needs to be re-run
----------------------------+-----------------------------------------------
  Reporter:  kowey          |        Owner:  ttuegel 
      Type:  defect         |       Status:  assigned
  Priority:  normal         |    Milestone:          
 Component:  Cabal library  |      Version:  1.6.0.1 
  Severity:  normal         |     Keywords:          
Difficulty:  unknown        |   Ghcversion:          
  Platform:                 |  
----------------------------+-----------------------------------------------

Comment(by ttuegel):

 Replying to [comment:9 tibbe]:
 > Replying to [comment:8 ttuegel]:
 > > Even with the patch I just attached, 'cabal configure' needs to be run
 first, but I doubt we want to change that behavior.
 >
 > I think we do! We already run configure automatically before build in
 most cases. I think we should always do that.

 OK, it's easy enough to configure and build before 'cabal test' or 'cabal
 benchmark'. Obviously, these commands have been updated to take the 'cabal
 configure' options, as well. I thought about installing dependencies, too,
 but decided against it: I don't think people expect 'cabal test' to
 install packages on their system, so it's probably not a good idea. Just
 checking, but is this the behavior you would expect, i.e., configure and
 build, but don't install missing dependencies?

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