Official upstream development repository for Cabal and cabal-install
Haskell Shell Python Logos Makefile Nix
Failed to load latest commit information.
Cabal Bump upper bound on time Feb 20, 2017
cabal-install Rename flag that enables expensive assertions. Feb 21, 2017
cabal-testsuite Unbreak the test suite. Feb 20, 2017
travis A few bug fixes to our CI setup. Feb 21, 2017
.arcconfig Add arcconfig, so arc diff works with Sep 24, 2015
.gitignore Move the test case to cabal-testsuite. Jan 19, 2017
.mailmap Update AUTHORS. Feb 20, 2017
.mention-bot Update .mention-bot Sep 16, 2016
.travis.yml Rename flag that enables expensive assertions. Feb 21, 2017
AUTHORS Update AUTHORS. Feb 20, 2017
LICENSE Update the copyright year, cont. (2) Jan 11, 2017 Clarify our policy on cabal-install support window. Jan 22, 2017
appveyor-retry.cmd Retry when running Appveyor to work around failures. Feb 8, 2017
appveyor.yml Run cabal-testsuite first when testing. Feb 19, 2017
cabal.project Make cabal-install a library. Feb 19, 2017
cabal.project.travis Enable hackage-repo-tool in CI Nov 27, 2016
default.nix update Nix expressions Dec 30, 2016
ghc-packages Rename the cabal directory to Cabal Oct 23, 2011
id_rsa_cabal_website.aes256.enc Rename a file. Jul 18, 2016
stack.yaml Make cabal-install use parsec parser Jan 26, 2017 Add || exit $? to all subshell calls Jul 27, 2016 A few bug fixes to our CI setup. Feb 21, 2017 Revert "Revert "Bump version."" Feb 17, 2017 A few bug fixes to our CI setup. Feb 21, 2017 Reimpelement gen-extra-source-files in Haskell Oct 14, 2016 Rename flag that enables expensive assertions. Feb 21, 2017 Add Travis job to build cabal with solver debug flags enabled. Oct 16, 2016 Add CI target for building Cabal using Stack Oct 9, 2016 Rewrite the test suite, AGAIN. (#4095) Nov 18, 2016

Cabal Hackage version Stackage version Build Status Windows build status Documentation Status

This Cabal Git repository contains the following packages:

The canonical upstream repository is located at

Installing Cabal

Assuming that you have a pre-existing, older version of cabal-install, run:

cabal install cabal-install

To get the latest version of cabal-install. (You may want to cabal update first.)

To install the latest version from the Git repository, clone the Git repository and then run:

(cd Cabal; cabal install)
(cd cabal-install; cabal install)

Building Cabal for hacking

The current recommended way of developing Cabal is to use the new-build feature which shipped in cabal-install-1.24. Assuming that you have a sufficiently recent cabal-install (see above), it is sufficient to run:

cabal new-build cabal-install

To build a local, development copy of cabal-install. The binary will be located at dist-newstyle/build/cabal-install-$VERSION/build/cabal/cabal; you can determine the $VERSION of cabal-install by looking at cabal-install/cabal-install.cabal.

Here are some other useful variations on the commands:

cabal new-build Cabal # build library only
cabal new-build Cabal:unit-tests # build Cabal's unit test suite
cabal new-build cabal-install:integration-tests # etc...

Running tests

Using Travis and AppVeyor. The easiest way to run tests on Cabal is to make a branch on GitHub and then open a pull request; our continuous integration service on Travis and AppVeyor will build and test your code. Title your PR with WIP so we know that it does not need code review. Alternately, you can enable Travis on your fork in your own username and Travis should build your local branches.

Some tips for using Travis effectively:

  • Watch over your jobs on the Travis website. If you know a build of yours is going to fail (because one job has already failed), be nice to others and cancel the rest of the jobs, so that other commits on the build queue can be processed.

  • If you want realtime notification when builds of your PRs finish, we have a Slack team. To get issued an invite, fill in your email at this sign up page.

  • If you enable Travis for the fork of Cabal in your local GitHub, you can have builds done automatically for your local branch seperate from Cabal. This is an alternative to opening a PR.

Running tests locally. To run tests locally with new-build, you will need to know the name of the test suite you want. Cabal and cabal-install have several. In general, the test executable for {Cabal,cabal-install}:$TESTNAME will be stored at dist-newstyle/build/{Cabal,cabal-install}-$VERSION/build/$TESTNAME/$TESTNAME.

To run a single test, use -p which applies a regex filter to the test names.

  • cabal-testsuite:cabal-tests is an executable runner for out-of-process integration tests for both the Setup interface, as well as cabal-install (if you pass the path to the executable to test via the --with-cabal flag). Most user-visible changes to Cabal should come with a test in this framework. See cabal-testsuite/ for more information about how to run tests and write new ones.

  • Cabal:unit-tests are small, quick-running unit tests on small pieces of functionality in Cabal. If you are working on some utility functions in the Cabal library you should run this test suite.

  • cabal-install:unit-tests are small, quick-running unit tests on small pieces of functionality in cabal-install. If you are working on some utility functions in cabal-install you should run this test suite.

  • cabal-install:solver-quickcheck are QuickCheck tests on cabal-install's dependency solver. If you are working on the solver you should run this test suite.

  • cabal-install:integration-tests are out-of-process integration tests on the top-level cabal command line interface. The coverage is not very good but it attempts to exercise most of cabal-install.

  • cabal-install:integration-tests2 are integration tests on some top-level API functions inside the cabal-install source code. You should also run this test suite.


  • Spaces, not tabs.

  • Try to follow style conventions of a file you are modifying, and avoid gratuitous reformatting (it makes merges harder!)

  • A lot of Cabal does not have top-level comments. We are trying to fix this. If you add new top-level definitions, please Haddock them; and if you spend some time understanding what a function does, help us out and add a comment. We'll try to remind you during code review.

  • If you do something tricky or non-obvious, add a comment.

  • For local imports (Cabal module importing Cabal module), import lists are NOT required (although you may use them at your discretion.) For third-party and standard library imports, please use explicit import lists.

  • You can use basically any GHC extension supported by a GHC in our support window, except Template Haskell, which would cause bootstrapping problems in the GHC compilation process.

  • Our GHC support window is five years for the Cabal library and three years for cabal-install: that is, the Cabal library must be buildable out-of-the-box with the dependencies that shipped with GHC for at least five years. The Travis CI checks this, so most developers submit a PR to see if their code works on all these versions of GHC. cabal-install must also be buildable on all supported GHCs, although it does not have to be buildable out-of-the-box. Instead, the cabal-install/ script must be able to download and install all of the dependencies (this is also checked by CI). Also, self-upgrade to the latest version (i.e. cabal install cabal-install) must work with all versions of cabal-install released during the last three years.

  • Cabal has its own Prelude, in Distribution.Compat.Prelude, that provides a compatibility layer and exports some commonly used additional functions. Use it in all new modules.

  • As far as possible, please do not use CPP. If you must use it, try to put it in a Compat module, and minimize the amount of code that is enclosed by CPP. For example, prefer:

    f :: Int -> Int
    #ifdef mingw32_HOST_OS
    f = (+1)
    f = (+2)


    #ifdef mingw32_HOST_OS
    f :: Int -> Int
    f = (+1)
    f :: Int -> Int
    f = (+2)

We like this style guide.


There are a few main venues of communication:

  • Most developers subscribe to receive messages from all issues; issues can be used to open discussion. If you know someone who should hear about a message, CC them explicitly using the @username GitHub syntax.

  • For more organizational concerns, the mailing list is used.

  • Many developers idle on #hackage on (archives). #ghc (archives) is also a decently good bet.


Notes for how to make a release are at the wiki page "Making a release". Currently, @23Skidoo, @rthomas, @tibbe and @dcoutts have access to, and @davean is the point of contact for getting permissions.

API Documentation

Auto-generated API documentation for the master branch of Cabal is automatically uploaded here: