On Dec 9, 2010, at 3:35 AM, Peter Simons wrote:
you said that a dependency of one of those packages would require
process >= 1.0.1.4. Now, what I don't understand is why you added
that restriction to hledger then?

Picture this common scenario, which I saw during installability testing - you install hledger to try it out. Cabal builds it with process 1.0.1.3. You get enthusiastic and later try to cabal install hledger-X, but this fails ("can not install hledger-X because hledger requires process-1.0.1.3").

(In other, similar-seeming cases I have seen cabal rebuild the installed depender; I don't understand all of cabal's behaviour.)

I presume the user could work around this by

- ghc-pkg unregister hledger; cabal install hledger-X
- installing hledger the first time with --constraint process-1.0.1.4

but I figured a low-impact to make things "just work" was to bump hledger's process dependency.

Is it making sense ? I welcome further insights or better solutions.

_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to