GitLab

Fixes #2130.

GhcOptions: use `NubListR` where appropriate. 

Some Cabal API clients apparently use `foldl mappend` on large lists of
`GhcOptions` records. Fixes #2110.

Nublist

User config fields like 'remote-repo', 'extra-prog-path' and 'build-summary'
were lists, which mean that when two SavedConfig types were concatentated
the lists for these fields were concatenated, resulting in duplicate entries.
Duplicated entries in these fields simply don't make sense, so we swicth to
NubList for these fields.

Closes: #2160

A NubList is a list where all elements are unique, but are maintained in
their original order. The Monoid NubList's mappend implement is just:

    NubList xs `mappend` NubList ys = NubList . nub $ xs ++ ys

which preserves NubList's required properties (ordering and unique-ness
of elements) and meets the requirements of the Monoid laws (identity,
associativity and closure).

These functions are from Mikhail Glushenkov's cabal/ghc-options-union
branch.

Fixes #2162.

Workaround for GHC issue 8825.

cabal-install/IndexUtils : Expose function getIndexFileAge.

* The function has type 'Repo -> IO Double'.
* It returns the age in days as a Double.
* Places that expected the age as an Int have been updated.
* Builds with ghc 7.4.2 and 7.8.3.

Add Cabal and cabal-install version numbers when writing a new config fi...

These values can be useful for debugging cabal issues.

Add license type UnspecifiedLicense.

Before this, AllrightsReservered had two separate meanings; the author
explicitly chose this license or not license was specified and therefore
defaults to AllRightsReserved.

The default license when no license is specified is now UnspecifiedLicense.

Closes: #2141

'support sandboxes' in bootstrap

Document building cabal from git sources and running the tests.

Add extra-ghci-libraries support to .cabal files

Remove redundant imports in cabal-install\Distribution\Client\

Bootstrap tweaks

database install

This changes how the SCOPE_OF_INSTALLATION variable is used to provide
an alternate way of running bootstrap.sh which can install
cabal-install to a separate prefix and package database without
altering the user's package database or using it. The idea with this
is to improve the repeatability of automatically installing ghc, cabal
and other haskell independently of the current standard installation
or the user's main package database.

Usage example:

ghc-pkg init /home/jake/test_cabal/
SCOPE_OF_INSTALLATION='--global --package-db=/home/jake/test_cabal/packagedb' PREFIX=/home/jake/test_cabal/prefix ./bootstrap.sh

If you don't override the SCOPE_OF_INSTALLATION variable, bootstrap.sh
works as before.

tarballs if these tarballs are already present.

A couple of settings were filtered out since
74cb2909 including
`configure-option`. However, it turns out you may want to
persist some options to `configure`, such as e.g.

  --configure-option=--build=x86_64-w64-mingw32

when working in a Cygwin host environment, but using a Mingw
toolchain (such as the one bundled with the Windows GHC bindist).

Approved by @dcoutts