16 Feb
2012
16 Feb
'12
11:25 a.m.
On Thu, Feb 16, 2012 at 8:17 AM, Thomas Tuegel
No, that's not what I'm trying to do. I had introduced a patch that ran tests for target packages and aborted installation if the tests failed. For example,
cabal install --enable-tests network
would install all network's dependencies (but not their tests), then build, test, and install network. It didn't change how dependencies were handled at all. However, the test runner in Cabal wasn't designed to be invoked from cabal-install: it sometimes exits on success, which cabal-install interprets as an error, even when it isn't. This was stopping packages without tests from being installed with 'cabal install --enable-tests', which shouldn't happen.
I see. Makes sense to me. Cheers, Johan