cabal-src: Alternative install procedure to avoid the diamond dependency issue.

[ bsd3, deprecated, distribution, program ] [ Propose Tags ]
Deprecated in favor of stack

Please see the file on Github for more information:

[Skip to Readme]


Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


  • No Candidates
Versions [RSS] 0.1, 0.2,, 0.2.1,, 0.2.3, 0.2.4, 0.2.5,, 0.3.0,,
Change log
Dependencies base (>=4 && <5), bytestring, conduit (>=1.1), conduit-extra, containers, directory, filepath, http-conduit (>=1.5), http-types, network, process, resourcet, shelly (>=1.3.1), system-fileio (>=0.3 && <0.4), system-filepath (>=0.4 && <0.5), tar (>=0.4 && <0.6), text, transformers [details]
License BSD-3-Clause
Author Michael Snoyman
Category Distribution
Home page
Source repo head: git clone git://
Uploaded by MichaelSnoyman at 2016-10-10T09:22:58Z
Reverse Dependencies 1 direct, 0 indirect [details]
Executables mega-sdist, cabal-src-install
Downloads 14937 total (27 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
Last success reported on 2016-10-10 [all 4 reports]

Readme for cabal-src-

[back to package description]

cabal-src is a package intended to help solve the Cabal diamond dependency problem.

The problem

Let's say you have three packages. foo depends on the text package, and can use any version of it. bar depends on text as well, but requires version 0.10.*. foobar depends on both of those.

If you upload these three packages to Hackage and install foobar, cabal will build foo and bar against the same version of text, and then build foobar against them. However, if you install these packages locally, foo will be built against the most recent version of text (currently 0.11.something), and then foobar will be unbuildable, since its dependencies depend on different versions of text.

You can see sample packages demonstrating the issue in the example folder.

This is just one example of the diamond dependency issue. When dealing with complicated systems such as Yesod, with dozens of packages that are in development, the situation becomes much worse.

Our solution

The important thing to note is that, if the packages are on Hackage, Cabal can handle the situation. The reason is that Cabal has enough information to calculate the correct versions of all dependencies to be used. So our goal is to give Cabal access to information on all dependencies, even those not yet on Hackage.

Instead of installing a local package with "cabal install", you can now use "cabal-src-install". This program actually calls out to "cabal install", and if that build succeeds, will perform the following steps:

  1. Create a source tarball via "cabal sdist"

  2. Copy this tarball into a special location in your .cabal folder.

  3. Update a 00-index.tar file specifically kept for cabal-src.

  4. Update your .cabal/config file to recognize the special cabal-src folder as necessary.

If you now install your "foo" and "bar" packages via "cabal-src-install", Cabal has full access to their source code. When it comes time to install foobar, Cabal can determine that foo can be recompiled with text 0.10 and will do so automatically.

Project status

This software should be considered alpha. We'll likely be using it for all Yesod development going forward, so I expect that alpha to be upgraded to beta and finally production quality in short order. All feedback is welcome!


Simply replace a call to "cabal install" with a call to "cabal-src-install". If you would like to only install the source tarball without actually installing the binary package, run it with "cabal-src-install --src-only".


This package now also includes the mega-sdist util, which handles uploading to Hackage from mega repos.

Compares local code against version on Hackage. Accepts the following options:

  • --gittag: Automatically tag as well.
  • --test: Automatically run cabal tests

Uses sources.txt to determine which packages to build.