Hi Judah, Op dinsdag 17 november 2009 15:34 schreef Judah Jacobson: > Do you actually need a new release of Haskeline? The latest release > of Haskeline (0.6.2.1) has the following constraint in its .cabal > file: > > utf8-string==0.3.* && >=0.3.1.1, > > So unless I'm missing something, I'd expect the existing release of > Haskeline to work fine with the future version of utf8-string that > you've described.
It does, but with the UTF-8 storage support darcs does not directly depend on utf8-string anymore. So either: * We depend on a new version of haskeline, that depends on a new version of utf8-string * We specify a utf8-string dependency in darcs.cabal, only to make sure the version haskeline uses is recent enough. The second option feels dirty, and I'm not sure if it works (if I compile haskeline against a buggy utf8-string, and then install 0.3.6 to keep the darcs installation happy, won't darcs still call the buggy utf8-string via haskeline?). That's why I suggested a new haskeline release. Regards, Reinier
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
