GitLab

Building the haddock docs requires building first. Arguably this is
a Cabal bug. It should probably generate the "autogen" files for
haddock and not just for build.

It did not actually contain any release notes and just
duplicated information in the README which was confusing.

The ',' character is not used as a separator and is allowed
within flag tokens. Fixes at least HsPerl5.

To make easier to track recent Cabal / cabal-install changes

Do it by just filtering that module out of the package
description before running sdist etc. This isn't lovely
because it steals that module name from the module namespace
but at least it now works. Thanks to Jean-Philippe Bernardy
for the first iteration of this patch.

Hopefully we can figure out a better fix for recent cygwin
versions of xargs which are apparently broken.

rolling back:

Wed Oct  8 08:44:10 PDT 2008  Clemens Fruhwirth <clemens@endorphin.org>
  * Also respect the max. command line size in Makefile driven builds

    M ./Distribution/Simple/GHC.hs -7 +13
    M ./Distribution/Simple/GHC/Makefile.hs -1 +1
    M ./Distribution/Simple/GHC/Makefile.in -1 +1

Thanks to Dimitry and Ross for identifying the problem.

When making packages like ghc-prim we need GHC to not automatically
try to link with base and haskell98.

Previously we said a package graph was inconsistent if two
dependencies on the same package name specified different
versions. Now we say that two such dependencies on different
versions are ok if there is a direct dependency between those
two package versions. So if your package graph ends up with
both base 3 and base 4 in it, then that's ok because base 3
directly depends on base 4, so we declare it not to be an
inconsistency. This removes the scary warnings at configure
time (fixing ticket #366) and also adjusts the invariant and
assertion of the InstallPlan ADT in cabal-install.

Ticket #323

We can still add more as necessary

Ticket #58. Does not yet include checking.

Allow flags, lib and exes in any order and handle unknown sections better.

eg "cabal -v configure" to mean "cabal configure -v"
For flags that are not recognised as global flags,
pass them on to the sub-command.

6.10.x was giving us 601 rather than 610.

Old aliases kept for compatibility

Ready to make the 1.6 branch

GHC < 6.10 put "$topdir/include/mingw" in rts's installDirs. This
breaks when you want to use a different gcc, so we need to filter
it out.