Recently there’s been quite a few things happening in the Arch Haskell community. Since Don stepped down from Arch Haskell work there have been quite a few changes in the community.
Before describing those changes I feel it’s worth pointing out just what Don has done over the last year or so. Pretty much single-handedly he has made sure that ArchLinux has almost all of Hackage available as native (source) packages. That resulted in ArchLinux being one of the best, if not the best, Linux distro for Haskell developers. In the end he maintained 1937 packages on AUR (there are currently 25237 packages on AUR in total), and he also wrote and maintained the tool used to track Hackage (cabal2arch).
So, what have we been up to since Don’s announcement?
First of all we’ve moved the activity to github. This allows us to maintain the packages as a team rather than put the entire burden on a single person. The source repositories,
archlinux-web are obviously where the source for the tool and its dependencies are kept. Furthermore there’s the
habs git repo. This repo contains the source for all the packages (
*.install files). Keeping all source packages on github will allow us to more easily accept updates and fixes to individual packages from people in the community. Unfortunately uploading to AUR still remains a bottle neck. Which conveniently brings me on to the ideas for the future.
Even though there now are two people who can upload packages AUR as arch-haskell, it is still likely to be a pain point in keeping up with the uploads to Hackage. The long-term solution is to stop using AUR, but for that to be possible we need to have some tool support for downloading and compiling packages from
archhaskell/habs. Until that tool support is there we’ll keep uploading to AUR.
In the future we would also like to provide a subset of the packages in binary form. The main issue at the moment is keeping on top of the re-building that is necessary (if package
foo is updated then all its dependants need to be re-built too). We are however well on our way towards having tools to support that. The next big issue is where to house the binary packages :-)
Even further into the future we will look closer at whether a repo of source packages really is the most effective way to track Hackage.
Even though we now have a few people who are hacking away on the tools, and try to keep up with Hackage, we can always use more help. So if you are interested in helping out this is a great opportunity to make a large impact. Just in this post I’ve mentioned a few areas where we need help:
cabal2archon new packages on Hackage, QA the results and then file pull requests against
- Getting tools that support downloading from
archhaskell/habsso we can move off AUR.
- Improving the tools used to build binary packages.
- Anything else you can think of.
- Last but not least, if you know a place where we could house binary packages, please let us know.
So, I encourage everyone with an interest in Haskell on ArchLinux to join the mailing list and get involved. No prior experience with Haskell is really necessary, a bit of shell (bash) scripting is enough for some of the planned things.
See you on the list!