#902: cabal install --enable-tests --only-dependencies fails to come up with a
complete install plan
---------------------------------+------------------------------------------
Reporter: tibbe | Owner: ttuegel
Type: defect | Status: new
Priority: normal | Milestone:
Component: cabal-install tool | Version: 1.8.0.6
Severity: normal | Keywords:
Difficulty: unknown | Ghcversion:
Platform: |
---------------------------------+------------------------------------------
Comment(by kosmikus):
I can see how this is broken at the moment. It has nothing to do with
--only-dependencies, as far as I can see.
There's a function in {{{Distribution.Client.Install}}} that enables tests
for command-line targets. However, that function only applies to targets
of constructor {{{SpecificSourcePackage}}}. Now if you type {{{cabal
install}}} in the current directory, the current directory is turned into
a {{{SpecificSourcePackage}}}. However, if you type {{{cabal install
foo}}}, then `foo' is ''not''. Dependencies aren't usually targets at all.
On the other hand, if you say {{{--enable-tests}}}, then ''all'' packages
are configured with tests enabled. So the solver sees a situation where
most package won't have tests enabled, but the builder will assume they're
all enabled.
So it looks like it should go wrong more often than not.
--
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/902#comment:1>
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
