我如何知道应该归咎于hackage不一致的人

时间:2015-03-31 08:30:15

标签: haskell dependencies cabal hackage

尝试安装criterion,我遇到了我想要重新安装的其他软件包的麻烦。重新安装它们会破坏一切(我已经尝试过了)。

$ cabal install criterion
Resolving dependencies...
In order, the following would be installed:
Glob-0.7.5 (new package)
abstract-deque-0.3 (new package)
abstract-par-0.3.3 (new package)
blaze-builder-0.4.0.1 (new package)
cereal-0.4.1.1 (new package)
erf-2.0.0.0 (new package)
ieee754-0.7.6 (new package)
hastache-0.6.1 (new package)
monad-par-extras-0.3.3 (new package)
parallel-3.2.0.6 (new package)
primitive-0.5.4.0 (latest: 0.6) (new version)
vector-0.10.12.3 (reinstall) changes: primitive-0.6 -> 0.5.4.0
aeson-0.8.0.2 +old-locale (reinstall) changes: mtl-2.1.3.1 -> 2.2.1
cassava-0.4.2.2 (new package)
mwc-random-0.13.3.2 (new package)
monad-par-0.3.4.7 (new package)
vector-algorithms-0.6.0.3 (new package)
vector-binary-instances-0.2.1.0 (new package)
vector-th-unbox-0.2.1.2 (new package)
math-functions-0.1.5.2 (new package)
statistics-0.13.2.3 (new package)
criterion-1.1.0.0 (new package)
cabal: The following packages are likely to be broken by the reinstalls:
yaml-0.8.10.1
stylish-haskell-0.5.11.2
hashtables-1.2.0.2
haskell-docs-4.2.5
Use --force-reinstalls if you want to install anyway.

现在,我如何找出是否责备criterion(使用太旧的依赖项)或其他软件包(因为没有足够的更新)?

1 个答案:

答案 0 :(得分:5)

都不是。这就是它的工作原理;使用库版本作为依赖项构建的包可能会很快变得不兼容。可能的组合数量太多了。

您有两种选择,基本上:

相关问题