GitLab

[ci skip]

GHC 7.4 is more than four years old now, well outside our three-year
support window. (Actually, GHC 7.6 is outside our support window too,
but I don't have any pending patches which are broken with that
version.)

More docs highlighting changes

Also makes 'cabal' a default highlighter

Basic cabal lexer for docs

Fix a space leak in package preferences (part of issue #3824).

The space leak was introduced in #3594. #3594 added a new variable,
sortedVersions, to sort the subtrees under package choice nodes in the search
tree. However, sortedVersions referenced the subtrees and caused them to be
retained when it was not used. This commit forces evaluation of
sortedVersions.

D.PD.Check: extra-doc-files only allowed when Cabal >= 1.18.

Document how solver quickcheck tests create valid ComponentDeps.

Only use the platform independent heuristics when we have to.
Also rename the functions to isAbsoluteOnAnyPlatform and isRelativeOnAnyPlatform
to make the distinction clearer.

This reverts commit e7d2a62c due to a
bug.

The package databases obtained from GHC_PACKAGE_PATH should be stored in
the LocalBuildInfo and passed to GHC when necessary; otherwise, the user
could change GHC_PACKAGE_PATH causing GHC and Cabal to see inconsistent
installed package sets. cabal-install should trigger reconfiguration if
GHC_PACKAGE_PATH changes.

Nub build targets, prevent duplicate output of component.

See https://github.com/haskell/cabal/pull/3722#issuecomment-244604918.

 Add the new hackage root keys for distribution with cabal (v2)

Validate InstallPlan in solver quickcheck tests, and update tests to handle executables.

Previously, the tests only evaluated enough of the result to determine whether
the solver found an install plan, but that install plan could be invalid.

Add `reconfigure` command

[ci skip]

[ci skip]

Fixes #2214 by adding a `reconfigure` command and invoking it whenever
necessary. The last configure flags used are saved in a
version-independent format so it should never be necessary for the user
to reconfigure manually.

@hvr

 reported that some component names were being reported
multiple times:

    ezyang@sabre:~/Dev/cabal-tmp$ cabal-shake new-build
    In order, the following will be built (use -v for more details):
     - Cabal-1.25.0.0 (lib) (file Cabal.cabal changed)
     - happy-1.19.5 (exe:happy, exe:happy) (dependency rebuilt)

This is because a build target was showing up multiple times in the
list, which can occur if we simultaneously build-depends and build-tools
on the same package.  So nub it out.
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

While at it, I updated a few urls I noticed to be outdated.

This is somewhat related to #3791

[skip ci]

Use platform independant isRelative.

The comment ending in \ turned the subsequent line of code
into a comment. This is due to the CPP language extension which is
turned on for this module.
Thus the 'isAbsolute' function failed to detect absolute
file paths on the form of DRIVE:\\PATH.

Move the isAbsolute and isRelative to the Utils module.
Use them throughout Cabal instead of the versions System.FilePath.

Compute profiling/shared based on library deps only.

Previously we'd build Cabal and custom setup dependencies
with profiling even though it wasn't necessary. Using a
refined dependency graph fixes the problem.

If looking at a Graph with different set of neighbors becomes
a common op, maybe we should add some functions to handle
this specific case.

Fixes #3789.
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>