Hi Mark,

I don't know what your approach is going to be for 'text' but if you will be including versions 1.0.* or 1.1.* you'll also need to pull in a newer version of 'parsec'. I've released parsec versions 3.1.4 & 3.1.5, whose only changes bump the 'text' dependency to 1.0.* and 1.1.* respectively.

Take care,

Antoine

On Fri, Jan 10, 2014 at 7:51 AM, Antoine Latter <aslatter@gmail.com> wrote:

I currently expect the change in parsec to be a simple change in the package description, so it will be fine for inclusion in the next platform if needed.

On Jan 9, 2014 7:47 AM, "Christian Maeder" <Christian.Maeder@dfki.de> wrote:
Hi,

I've just noticed that text-1.1.0.0 was uploaded and that the (earlier adapted) constraint (text >= 0.2 && < 1.1) for parsec-3.1.4 is again too narrow.

http://hackage.haskell.org/package/text
http://hackage.haskell.org/package/parsec

I assume text-1.1.0.0 is an improvement that should go into the platform, but the platform cannot keep track with such rapidly moving targets like the text package.

When can we expect the text package to become more stable?
Which text (and parsec) version should go into the next HP release?

Cheers Christian

Am 06.01.2014 12:29, schrieb Christian Maeder:

Hi,

I would propose to update to the latest text-1.0.0.1 version and other
packages depending on it (ie. parsec-3.1.4)

(A name containing 2014 would make more sense to me.)

Cheers Christian