[arch-haskell] Starting to help

Fabio Riga rifabio at gmail.com
Sat Oct 12 07:39:26 UTC 2013

Hi all,

yesterday I submitted a patch to HABS repository just because I met
some out-of-date packages in AUR. Then I read the "story" of this
group in this mailing list and thought that I can give some help. I
think I can take responsibility for a bunch of packages and care for
updates, but I need some hints.

1) In order to test for broken packages, do I really need to use the
makeworld script? I think it would take too much time! I would prefer
to simply compile what I use, also to find if makepkg can resolve
dependencies. Launching makeworld in another directory with only my
packages would do the job?

2) Past discussions suggest me that the group is centred on a small
number of packages to put in a binary repository. It's wonderful to
have this, but it takes a very long time. What do you think if some
people concentrate in the simplest and fastest task of preparing
PKGBUILDs and put them in a place (i.e. AUR) where the core group
decide witch package worth an inclusion in the repo? Haskell
repository would actually be an expanded and specialised version of
Community repo. Anyway I'd prefer the mainter to be the group, not a
single. That's only my opinion, of course.

3) For Peter: could you please give some help information on how to
use the scripts in
https://github.com/peti/arch-haskell/tree/master/scripts ?

4) Why haskell packages in extra depends on ghc-7.0.3 (still in testing)?

Tha's all for now. Sorry for my bad English!


More information about the arch-haskell mailing list