On Wed, Jan 28, 2009 at 16:14:17 +0100, Petr Rockai wrote: > - regex-compat >= 0.71 && <= 0.92, > + regex-compat >= 0.71 && < 0.94,
Not sure about this one. We'd have to check what we're using regexes for, and if we care about this. Can you do a quick search? (the fact that darcs has worked from 0.71 to 0.92 makes me think it's unlikely we're doing anything fancy enough that a potentially non-backward API compatible change could affect us, but let's just make sure it's safe) > - parsec >= 2.0 && < 2.2, > + parsec >= 2.0 && < 3.1, The parsec limit is because I'm slightly afraid of breaking OldDate. This is the third time this has come up... Duncan has suggested we just stick with 2.1 if we aren't sure. David himself has submitted a similar patch, but that was when he was thinking it was just matchers. He hasn't yet responded when I pointed out the OldDate problem. The safe route is just to ask Zooko to install parsec 2.1 -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
