Hey guys, The first cut at public scripts for group maintainership of packages in in the arch-haskell package in AUR. This is very much an experimental release. If you play with these scripts, I'd love some feedback and patches. These are most of the tools I use to manage the AUR / Hackage project, including: * Get a list of all packages maintained by arch-haskell $ mypackages | sort > arch-haskell-packages.txt $ wc -l arch-haskell-packages.txt 1873 arch-haskell-packages.txt * Generate the Hackage <-> AUR mapping file for Hackage. $ distro-map --> creates http://www.galois.com/~dons/cabalArchMap.txt used by Hackage. TODO: host this in the code.haskell.org/arch repo, for group maintainership, update Hackage to look here. * Generate the QA report of versions, build success etc. + Assumes you have the arch-haskell-packages.txt file (generated above), + and a ~/.build-all.log with format "haskell-parameterized-data True" indicating build status + uses the download stats for Hackage: http://www.galois.com/~dons/hackage/hackage-downloads.csv $ arch-report --> creates http://code.haskell.org/arch/arch-haskell-status.html * find the AUR url for a package: $ get-arch-url haskell-json http://aur.archlinux.org/packages.php?ID=17480 Some of these tools are hacked enough that they assume the user has files that you might not have access to, however, they should give you an idea of some of the tasks that can be automated. Not included are the shell scripts for updating the RSS feed (yet). My plan is to continue to: * keep documenting the group maintainer process, http://haskell.org/haskellwiki/Arch_Linux/Arch_Haskell_Group_Maintainership * improve and simplify the scripts so they can be easily installed by any future arch-haskell group maintainers * once the arch-haskell package process is all sorted and repeatable, do some training with gour et al to begin group maintainership. -- Don