> the package http://hackage.haskell.org/package/haskelldb-hdbc-mysql/ the use
> of HDBC <2.3.0
> I'm using cabal-install 0.14, and with a fresh install (no packages already
> installed), cabal-install tries to install HDBC-2.1.1 instead of, say,
> The problem is that HDBC-2.1.1 is old (2009) and does not compile.
> When I download haskelldb-hdbc-mysql manually, change the dependency and
> then install, it compiles fine.
> Is the dependency ill-declared, or is that a cabal problem?
Apart from the change of license, there were no serious changes to the
HDBC interface between the 2.2.* and 2.3.* series: as far as I know,
it should be fine to change the dependency. That said, I've not worked
with haskelldb-hdbc-mysql, so I can't say for sure.
On 12-07-04 10:58 AM, Yves Parès wrote:
> the package http://hackage.haskell.org/package/haskelldb-hdbc-mysql/ the
> use of HDBC <2.3.0
> I'm using cabal-install 0.14, and with a fresh install (no packages
> already installed), cabal-install tries to install HDBC-2.1.1 instead
> of, say, HDBC-22.214.171.124.
HDBC 2.2.* all want time>=126.96.36.199 && <=188.8.131.52, GHC 7.4.1 comes with
time-1.4, therefore HDBC 2.2.* are all rejected. 2.1.1 is the topmost
one without the upper bound.
This analysis is made possible by "cabal install --dry-run -v3
haskelldb-hdbc-mysql" of cabal-install 0.14. Now with actually relevant
output! (As part of the new "modular" solver, I guess.)
P.S. haskelldb-hdbc wants mtl-2.0.*, but you already have mtl-2.1
because you have cabal-install 0.14. mtl-184.108.40.206 in turn wants
transformers-0.2.*, but you already have transformers-0.3.0.0 again
because you have cabal-install 0.14. Expect mysterious problems in the