But I think it should be like this, right?
Say ghc provids process-old, and Cabal-old depends on it. Then I use
--upgrade-dependencies to install somePackage and so install process-new in
user space. The process-old is still there. Why Cabal-old breaks and
`ghc-pkg check` gets nothing?
On Wed, No
On 12-11-19 09:39 PM, Magicloud Magiclouds wrote:
And, the key point is that using upgrade-dependencies with
cabal-install. I am using git (current) version of cabal-install.
Without that argument, things could be fine. With it, it must fail.
Therefore, don't use upgrade-dependencies.
Not only shadowing.
For example, when I installed warp-static, yesod, or gtk2hs. A
clear-user-space may ease the problem and got them installed. But normally
with a not brand new user space, it failed like above.
And, the key point is that using upgrade-dependencies with cabal-install. I
am using g
On 12-11-19 04:45 AM, Ivan Lazar Miljenovic wrote:
On 19 November 2012 18:21, Magicloud Magiclouds
wrote:
: cannot satisfy -package Cabal-1.16.0:
Cabal-1.16.0-dd0ce1db6fea670a788547ee85411486 is unusable due to missing
or recursive dependencies:
directory-1.2.0.0-8edf300597b0da609c8
On 19 November 2012 18:21, Magicloud Magiclouds
wrote:
> Hi,
> I am having ghc 7.6.1 working here. But anytime I installed something with
> cabal-install, I got prompts like:
>
> Warning: The following packages are likely to be broken by the reinstalls:
> haskell98-2.0.0.2
> ghc-7.6.1
> Cabal-1.
