The main user of parsec -- pandoc -- is *not* going to move to parsec 3,
since it is twice as slow.
That means that neither is the Haskell Platform
That means that we should downgrade to parsec 2 on arch and *not move to
parsec 3 for the foreseeable future*.
-- Don
----- Forwarded message from John MacFarlane
Hi John,
Suppose you're using pandoc in a web app that delivers up hundreds of pages, some quite long.
if you do that, Pandoc is a mission-critical component in your setup and it's fine to dedicate extra effort to, say, building it with Parsec 2. For occasional users like me, however, the difference in performance is hardly measurable.
Well, if you don't want your software to work on ArchLinux, then this is the way to go. It's your choice.
It's not my fault that it doesn't work on Arch.
Of course it is. You deliver a cabal file that refuses to build Pandoc with Parsec 3, even though it would build just fine! Who else do you think should be responsible for that?
Anyway, I have found a solution that should work. I'll fix Pandoc's Cabal file and upload that version to Hackage calling it, say open-pandoc. The automatic cabal2arch converter will make that package available in ArchLinux within a couple of days, and then everything will be fine.
Take care, Peter
----- End forwarded message -----