Hi Thomas. > 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.
Actually, the new solver will filter out --enable-tests for packages that don't define any. If the old solver could do the same, would that be an alternative to patch the Cabal lib? Cheers, Andres -- Andres Löh, Haskell Consultant Well-Typed LLP, http://www.well-typed.com _______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
