I'm not sure how it would help users experiment with patched files since
#427: how to access temporary build-files/logs? ----------------------------+----------------------------------------------- Reporter: claus | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.8.3 | Platform: ----------------------------+----------------------------------------------- Comment (by claus): Replying to [comment:1 duncan]: presumably we have to unpack the tarball from fresh, the idea of randomly re-using old build temporary trees makes me rather nervous. Nothing random there, just the ability to continue from the point of failure. Your build log tells you what commands cabal used. One of them failed. You edit the command line to see whether you can fix the issue. But to run and test the modified commandline, you need the temporary build directory in the state in which that previous command failed. Once your modified command succeeds, you know whether you need to fix your package or cabal or ghc or .. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/427#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects