#945: Fails to find install plan for containers package tests
---------------------------------+------------------------------------------
Reporter: tibbe | Owner: kosmikus
Type: defect | Status: assigned
Priority: high | Milestone: cabal-install-0.16
Component: cabal-install tool | Version: 1.14.0
Severity: major | Keywords:
Difficulty: unknown | Ghcversion: 7.4.1
Platform: Linux |
---------------------------------+------------------------------------------
Changes (by kosmikus):
* keywords: solver =>
* milestone: cabal-install-0.14.2 => cabal-install-0.16
Comment:
Ok, I can confirm the problem by using the Github version of containers on
a plain ghc-7.4.1 installation.
The problem is actually not a solver problem, as I first thought, but a
more fundamental problem in Cabal. It's also independent of using the
modular solver.
So the problem here is that the testsuite of containers *indirectly*
depends on containers again. The question is whether this should be
allowed.
Fixing this would indeed mean that we should be able to build containers
first, then the dependencies of the test framework, and finally the
testsuite. We'd indeed have to introduce a possibility to build flavours
or parts of packages in isolation. It'd for example be nice to be able to
separately build non-profiling and profiling versions of a lib.
However, I'm afraid this change will take some more careful design, so
don't expect a quick fix.
--
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/945#comment:2>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects
_______________________________________________
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel
