GitLab

Since Cabal-1.4 we've been able to parse versioned licenses
and unknown licenses without the parser falling over.

It's pretty meaningless since it's only a syntactic check.
The proper thing is to maintain a dependency set or to
simplify dependencies before printing them.

Instead of matching on the actual expression ">= x.y" we use the
sematic view of the version range so we can do it precisely.
Also use foldVersionRange to simplify a couple functions.

It's still possible to build with ghc-6.4 but you have to pass
extra flags like "ghc --make -cpp -fffi Setup.hs" We could not
keep those OPTIONS pragmas and make it warning-free with ghc-6.10.
See http://hackage.haskell.org/trac/ghc/ticket/2800 for details.

Export constructor functions and deprecate all the real constructors
We should not be pattern matching on this type because it's just
syntax. For meaningful questions we should be matching on the
VersionIntervals type which represents the semantics.

Also add simplify and isNoVersion.

as a sequence of non-overlapping intervals. This provides a canonical
representation for the semantics of a VersionRange. This makes several
operations easier.

Use it to simplify the eval / withinRange function

It requires cabal-version: >= 1.6 to be specified

It requires Cabal-1.6 or later.

Rather than encoding them in existing constructors.
This will enable us to check that uses of the new syntax
are flagged in .cabal files with cabal-version: >= 1.6

Yes, LHC really does use ghc-pkg (with a different package.conf)

So it uses libdir=$prefix/lib rather than libdir=/usr/local/lib

Support for LHC is the first divergence between 1.7
and the stable 1.6.x series.

On newer GHCs using {-# OPTIONS_GHC -fffi #-} gives a warning which
can lead to a compile failure when -Werror is activated.  We therefore
emit this option if we know that the LANGUAGE pragma is supported 
(ghc >= 6.6.1).

Fixes ticket #389

This happened when the lib used pkg-config but the exe did not.
It cropped up in hsSqlite3-0.0.5.

Variant on a patch from Bryan O'Sullivan

Avoid chicken and egg problem. We cannot upload Cabsl-1.6 to
hackage until hackage is using Cabal-1.6 if it uses features
that are introduced in 1.6. So just comment them out for now.

Makes it possible for alex and happy to work with cabal-1.2 -> 1.6