Bitwise Evolution

Musings of a Portland-area hacker bent on improving digital lifestyles.

Cabal-dev: Sandboxing Your Haskell Development (and Now With Ghci!)

Reproducing builds is pretty much essential if you intend to do sustainable software development, and while it’s generally possible, it’s been fairly difficult to do so with Haskell. One of the challenges has been that there are only generally two local databases of installed packages for any given (user, ghc-version) pair. Each ghc install has a global package database, and each user has a user package database for each version of ghc. This is perfectly suitable in most situations, but it becomes problematic when you need conflicting packages to be installed for disparate development projects. Cabal-dev removes the user package database from the picture, and it is relatively simple (with some self-control :) to maintain a minimal global package database: just don’t install anything system-wide with cabal.

Cabal-dev does this by creating a per-project sandbox that contains a package database of all the dependencies as well as the project under development. Therefore, it was simple to add support for launching ghci with this package database in place of the user package database. That’s been added in cabal-dev-, which is available on hackage now, allowing you to do things like this (using my Haskell Version Space Algebra library as an example):

$ cd havsa $ ls LICENSE Setup.hs src/ versionspaces.cabal $ cabal-dev install Resolving dependencies... Configuring mtl- Preprocessing library mtl- Building mtl- [ 1 of 21] Compiling Control.Monad.Identity ( Control/Monad/Identity.hs, dist/build/Control/Monad/Identity.o ) .... Registering VersionSpaces-0.0... Installing library in /home/creswick/development/havsa/cabal-dev//lib/VersionSpaces-0.0/ghc-6.12.3 Registering VersionSpaces-0.0... $ cabal-dev ghci GHCi, version 6.12.3: :? for help Loading package ghc-prim ... linking ... done. Loading package integer-gmp ... linking ... done. Loading package base ... linking ... done. Loading package ffi-1.0 ... linking ... done. Prelude> :m + AI.VersionSpaces Prelude AI.VersionSpaces> showBSR EmptyBSR Loading package syb- ... linking ... done. Loading package base- ... linking ... done. Loading package mtl- ... linking ... done. Loading package logict-0.4.1 ... linking ... done. Loading package VersionSpaces-0.0 ... linking ... done. "Empty" Prelude AI.VersionSpaces>

This is still far from perfect: you can’t easily load code into the ghci session without exiting, re-running cabal-dev install and cabal-dev ghci, but it’s a good start.