[arch-haskell] How to currently install haskell packages?

Thomas Dziedzic gostrc at gmail.com
Sat Oct 12 07:40:05 UTC 2013

On Sat, Mar 3, 2012 at 4:06 AM, Magnus Therning <magnus at therning.org> wrote:
> On Fri, Mar 02, 2012 at 02:46:53PM +0100, Alessandro Pezzoni wrote:
>> > `ghc-paths` used to be in [extra]/[community] at some point, I wonder
>> > why it was removed.
>> I tried adding it to habs but I couldn't do that, because it is
>> already there as a base package. I can't remove it either without
>> removing all its dependants first.
>> Should I leave this alone until we figure out why it was removed?
> I've just made an attempt at adding ghc-paths to [haskell], but I
> failed because [extra]/[community] is broken:
> - one of the packages that depend on ghc-paths also depends on
>  deepseq, and
> - deepseq is gone from [extra]/[community], so I added it too to
>  [haskell], but
> - one of the packages that depend on deepseq also depends on text, and
> - text in [extra]/[community] depend on deepseq
> This effectively prevents me from fixing [haskell] until
> [extra]/[community] is fixed!
> This episode has made me consider whether the tight dependency between
> [haskell] and [extra]/[community] should be broken in the future.


Removing deepseq was a mistake and I should have waited until after
moving the new ghc (since ghc 7.4.1 now provides it.) to extra.

I don't think it's worth fixing it right now because I plan to move
the new ghc today or tomorrow so just hold off all rebuilds against
extra/community for now.

The main focus in this rebuild was to cleanup the haskell situation on
arch and reorganize it so there is a new direction for it rather than
having it stagnate and leaving it in a frozen state essentially.

It's really only been a week since I began my cleanup of haskell so
please give it a little more time and patience before making a major
Some of the issues brought up during the haskell rebuild need lots of
time and communication with upstream which takes time.
I would prefer it if we could work together on any issues you might
have with haskell on arch.

Don't hesitate to open up lots of bugs on the bug tracker so we can
discuss each issue more thoroughly and so I wont forget. :)


More information about the arch-haskell mailing list