[arch-haskell] [jgm at berkeley.edu: Re: Pandoc restriction for Parsec <3]
magnus at therning.org
Sat Oct 12 07:36:11 UTC 2013
On 16/02/10 01:09, Don Stewart wrote:
> 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*.
Is there any plan to still provide parsec 3 in Arch?
As we all know, GHC is capable of having several versions of one package
installed. Pacman needs separate names for the packages, but that feels like
a minor issue. The only issue I see is with cabal2arch (since we want it as
automated as possible). Can cabal2arch handle it?
A possibly naive idea would be the following:
- pacman package "parsec" is parsec 2
- pacman package "parsec3" is parsec 3
- cabal2arch maps dependencies on "parsec >2" to "parsec3", and all other to
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: magthe
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: OpenPGP digital signature
More information about the arch-haskell