Hi,
I noticed a weird behaviour with cabal-install. When I run `cabal install
hspec --dry-run -v` cabal-install correctly picks hspec-1.4.3 (the latest
version).
However, when I run `cabal install ansi-terminal hspec --dry-run
-v`cabal-install tries to install hspec-0.3.0 for no apparent reason.
Aha!
I think I know why this happens.
The latest versions of ansi-terminal and hspec do not work together. Cabal
picks the latest ansi-terminal (0.6) first, then the latest hspec that
doesn't conflict with this choice is 0.3.0.
I can confirm this by the following:
$ cabal install hspec ansi-ter
On 25 January 2013 14:46, Ozgur Akgun wrote:
> The latest versions of ansi-terminal and hspec do not work together. Cabal
> picks the latest ansi-terminal (0.6) first, then the latest hspec that
> doesn't conflict with this choice is 0.3.0.
If this happens because the dependency bounds of ansi-te
Hi Max,
On 25 January 2013 15:58, Max Bolingbroke wrote:
>
> If this happens because the dependency bounds of ansi-terminal are too
> tight then please send me a patch.
No, actually it happens because hspec depends on ansi-terminal-0.5.*.
I am cc'ing Simon Hengel, the maintainer of hspec so he
Hi Ozgur,
I'm missing some context here, but I'll release an updated version of
hspec ASAP ;)
Cheers,
Simon
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
