October 2010 - arch-haskell

Make-based incremental build for arch-haskell
by Peter Simons 22 Oct '10

22 Oct '10

Hi, I have created a fairly simple GNUmakefile to perform incremental builds of the arch-haskell repository (a.k.a. "habs"). The code can be accessed by means of Git as follows: git clone http://git.cryp.to/arch-haskell The repository is very small -- currently, it builds only pandoc, hledger, and uulib (plus all packages that these three depend on). The set of packages is determined by a bunch of symbolic links that are part of the repository: ~/src/arch-haskell$ ls -l src/*.cabal lrwxrwxrwx 1 simons users 27 Oct 22 13:44 src/binary.cabal -> binary/0.5.0.2/binary.cabal lrwxrwxrwx 1 simons users 19 Oct 22 13:44 src/csv.cabal -> csv/0.1.1/csv.cabal lrwxrwxrwx 1 simons users 27 Oct 22 13:44 src/digest.cabal -> digest/0.0.0.8/digest.cabal lrwxrwxrwx 1 simons users 28 Oct 22 13:44 src/hledger.cabal -> hledger/0.12.1/hledger.cabal lrwxrwxrwx 1 simons users 36 Oct 22 13:44 src/hledger-lib.cabal -> hledger-lib/0.12.1/hledger-lib.cabal [...] As you can see, these links refer to the Hackage database, which is supposed to be copied into the src/ directory as well. The make target "update" will do that automatically. Given those files, "make all" ... - generates a PKGBUILD for every Cabal package, - compile the package, and - and registers the package in the Pacman database. If you'd like to try out the build, run these commands in a freshly checked-out copy of the <http://git.cryp.to/arch-haskell> repository: # Populate the src/ directory with a recent version of Hackage. make update # Unregister Haskell packages from Pacman to make sure that the # following builds don't have any hidden dependencies. make clean # Build all packages (pandoc, hledger, and uulib). make Instead of building all targets, it's also possible to build only selected targets by running "make haskell-zlib" or "make hledger". Now, the GNUmakefile needs to map package names from Cabal to ArchLinux. Currently, this is accomplished using a hard-coded list. For example, hledger needs the following variable assignment hledger_name = hledger to tell make that this package deviates from the normal "haskell-NAME" scheme. Obviously, this list ought to be generated automatically from the information contained in the haskell-Ashlin's library, but I haven't yet automated the task. Furthermore, make needs dependency information about the packages. This know-how, too, is currently hard-coded in the GNUmakefile. For example: $(pandoc_tarball) : $(HTTP_tarball) $(xhtml_tarball) $(texmath_tarball) $(zip-archive_tarball) $(network_tarball) : $(parsec_tarball) $(HTTP_tarball) : $(network_tarball) $(texmath_tarball) : $(xml_tarball) $(parsec_tarball) $(zip-archive_tarball) : $(digest_tarball) $(zlib_tarball) $(binary_tarball) Maintaining that information manually is out of question, IMHO, and we really ought to generate that information from the Cabal files. I'm not yet sure how to do it, though. Anyway, let me know what you think. Take care, Peter

3 3

For one of the Arch devs, please fix haskell-cgi
by Magnus Therning 22 Oct '10

22 Oct '10

I just raised a bug against haskell-cgi[1]. I bumped into this as I was trying to compile binary packages for all of haskell-platform. Once this bug is closed I can upload the binaries to a public repo. /M [1]: https://bugs.archlinux.org/task/21412 -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe

1 0

Re: [arch-haskell] Layout of ABS tree for Haskell packages?
by Rémy Oudompheng 21 Oct '10

21 Oct '10

On 2010/10/20 Xyne <xyne(a)archlinux.ca> wrote: > Just to be clear, this is not what I meant by "the translation table of Hackage > names to Arch names", but this is part of the general metadata I mean in > general. What I had in mind at the time was the HackageDB -> Arch name > translation table. > > Basically all metadata that may change should be available in simple > parsable formats via (logically organized) direct links and maybe even as > an archive containing all such metadata files. In this case, we should switch our main repository to use a single plain text file (e.g. PKGLIST) used by the manycabal2arch program, or by a Makefile rule, to generate the habs repository. The PKGLIST file would be fed to some script that generates the table you're referring to and uploaded to a/the website as I think it was before we became the team. -- Rémy.

5 9

Layout of ABS tree for Haskell packages?
by Magnus Therning 19 Oct '10

19 Oct '10

I've just downloaded all 1937 packages maintained by arch-haskell on AUR, and I'm about to put them all in a git repository. Before doing that I thought I'd ask if anyone has suggestions on the directory hierarchy in that repo? The only criterion I can think of is that we'd probably would want binary and source packages separated in some way. I should say that this is mostly a hunch on my part so I'm more than willing to be convinced otherwise. So, based on this hunch I'm currently leaning towards the following layout: habs ├── bin │ ├── befunge93 │ │ └── PKGBUILD │ ├── berp │ │ ├── berp.install │ │ └── PKGBUILD │ │ ... ├── aur │ ├── addlicenseinfo │ │ └── PKGBUILD │ ├── advgame │ │ └── PKGBUILD │ │ ... Any thought or comments on this. I'm particularly interested in comments from people who have experience with working with the ABS-related tools. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe

5 13

Re: [arch-haskell] How to update packages in extra?
by Rémy Oudompheng 19 Oct '10

19 Oct '10

On 2010/10/18 Rémy Oudompheng <remyoudompheng(a)gmail.com> wrote: > On 2010/10/18 Magnus Therning <magnus(a)therning.org> wrote: >> On Mon, Oct 18, 2010 at 14:17, Peter Simons <simons(a)cryp.to> wrote: >>> Hi, >>> >>> the PKGBUILD files in "extra" have been generated with ancient versions >>> of cabal2arch, like 0.4.1, and because of that they lack features such >>> as the generation of Haddock reference documentation. Is there any way >>> for us to update those files? Who has the ability to do that? >> >> You'll need an Arch dev to do that. Raise a bug on the bugtracker for >> the package in question. > > I'll do that. Maybe I'll take the opportuniy to add haskell-tar as an > official package, since it is a dependency of the archlinux library > now. For the moment I only did mtl, quickcheck and parsec. The packages in [extra] are different from what is output by cabal2arch in the sense that they enable shared libraries, profiling libraries and split-object files. -- Rémy.

4 3

AUR Comment for haskell-abortt-transformers
by aur-notify＠archlinux.org 19 Oct '10

19 Oct '10

from http://aur.archlinux.org/packages.php?ID=40580 magus wrote: A test comment, I need to work out the settings for arch-haskell. --- If you no longer wish to receive notifications about this package, please go the the above package page and click the UnNotify button.

4 9

New team, new logo?
by Xyne 18 Oct '10

18 Oct '10

Hi, This has no real importance whatsoever but I want to propose the adoption of the Arch Haskell logo that I made a while ago. It's just a simple combination of the (no longer so) new Haskell logo and the Arch logo. I think I posted it on the blog but it never got a response. You can find a png and an svg version on the following page: http://xyne.archlinux.ca/img/arch_linux_programming_language_logos/ Regards, Xyne

3 3

Topological Build Queue Script
by Xyne 16 Oct '10

16 Oct '10

Hi, I've written a script (in Haskell) that accepts package names on the command line and returns a topologically-sorted list of those packages and all others that depend on them, directly or indirectly. The script parses the output of "pacman -Qi", specifically the "Required By" field, to generate the directed dependency graph. The subgraph of that graph that is reachable from the specified packages is then passed to Data.Graph.topSort to generate the list. I have assumed that the "Required By" field is complete and that it correctly displays relationships for packages that depend on "provided" packages. Because the script parses "pacman -Qi", all of the packages must be installed. It would also work for "pacman -Si" and it can be easily extended later to handle other input such as formatted data from .cabal files or custom output from cabal2arch. The could could also be adapted for extracting other information from Pacman. You can find it under the name "topac" here: http://arch.localhost:35620/scripts/haskell/#topac Regards, Xyne

2 4

Error messages from FindCLibs
by Rémy Oudompheng 15 Oct '10

15 Oct '10

The FindCLibs function in cabal2arch (which I want to include in the archlinux library) report errors for non-Haskell dependencies it cannot translate into ArchLinux package names. Batch running cabal2arch can find some missing items : I attached a list of candidates. We basically have to run "pkgfile lib$i.so" for $i in this file (pkgfile is a script from the pkgtools package) to know the package name corresponding to a library name. -- Rémy.

2 1

Some changes to the github repos
by Magnus Therning 14 Oct '10

14 Oct '10

Remy has done some rather low-level work on the archlinux git repo, splitting it into two repos. Unfortunately this means that all existing clones are likely to be very broken at the moment. Given how soon after the creation of the github repos this was done, I'm not expecting it to cause major grief. Also note that this *only* affects the archlinux repo, the habs and cabal2arch repos are untouched by this. With this I feel we are in a good position to announce to the large Arch community of the changes to how Haskell is handled in Arch, together with the plans for the future. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe

3 4