#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 tibbe): Replying to [comment:11 ttuegel]:

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?

I think it's a good compromise for now. I'd prefer if (and have argued for) `cabal build/test/bench` to "do what I mean." Until we all agree that they should install dependencies etc I think having `cabal test` imply `cabal configure` and `cabal build` is a good compromise for now. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/592#comment:12 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects