cabal-devel

Download

cabal-devel@haskell.org

March 2012

6 participants
192 discussions

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 01 Mar '12

01 Mar '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Comment(by tibbe): Replying to [comment:5 ttuegel]: > We've discussed this before, and I think the conclusion we came to was that 'cabal test' should run 'cabal build' if necessary, but we should not change the behavior of './Setup test'. Is that still the consensus? Sounds good to me. > I'm not sure what was meant by "it becomes clear what needs to be rebuild because we actually have accurate information about it." Maybe this is naive, but I think if we simply call 'cabal build' before running 'cabal test', it will only rebuild what needs rebuilding. That is, I think all the checks we need are in place already. Am I missing something? Nope. Just run `cabal build` before. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:6> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 01 Mar '12

01 Mar '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Comment(by ttuegel): Replying to [comment:4 tibbe]: > We now have a test-suite section so this should be feasible to address. Thomas, what do you think? We've discussed this before, and I think the conclusion we came to was that 'cabal test' should run 'cabal build' if necessary, but we should not change the behavior of './Setup test'. Is that still the consensus? I'm not sure what was meant by "it becomes clear what needs to be rebuild because we actually have accurate information about it." Maybe this is naive, but I think if we simply call 'cabal build' before running 'cabal test', it will only rebuild what needs rebuilding. That is, I think all the checks we need are in place already. Am I missing something? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Jump to page: