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

Add Travis job to build cabal with solver debug flags enabled.

Add explicit osx image to GHC 7.8.4 job

Duncan Coutts authored 8 years ago and Herbert Valerio Riedel committed 8 years ago

Change the minimum version we use to decide if ghc supports .ghc.env
files. Previously we declared that it required 8.0.2, but 8.0.2 is not
out yet so this makes things hard to test.

It was fixed in the 8.0.x branch at the end of August, so if ghc
declares itself to be 8.0.1.$date from September or later, then it's ok.

Duncan Coutts authored 8 years ago and Herbert Valerio Riedel committed 8 years ago

This is most of the way there but needs testing in practice with
ghc-8.0.2.

Duncan Coutts authored 8 years ago and Herbert Valerio Riedel committed 8 years ago

When we invoke ghc in Cabal it's impostant that we control the
environment. It's already the case that ghc ignores the .ghc.env files
when we use -hide-all-packages, but there were a few places where we
were not using this.

Duncan Coutts authored 8 years ago and Herbert Valerio Riedel committed 8 years ago

This new ghc feature was actually added in ghc 7.10 but very limited,
then extended significantly in 8.0.1 but with a severe bug for our use
case and then should be working fine in 8.0.2 onwards.

This patch adds basic support for writing .ghc.environment files. This
feature will be used later in cabal-install, but it makes sense for the
functionality to live in Cabal next to the other code that knows all
too much about GHC.

.ghc.environment file support works in ghc 8.0.2 onwards

It was actually added in ghc 7.10 but very limited, then extended
significantly in 8.0.1 but with a severe bug for our use case and
then should be working fine in 8.0.2 onwards.

Fix gen-extra-source-files.hs

Reimpelement gen-extra-source-files in Haskell

- No need to add other-modules by hand
- Works on OSX (.sh didn't)
- Found missed files!

Rename 'backpack-includes' to 'mixins'.

Initial impl of maintaining project build status

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

We construct a PostBuildProjectStatus which has sets of package ids
covering various properties, including:
 - out of date
 - definitely up to date
 - probably up to date
 - invalid due to dep changes
 - invalid due to direct build failure

We also persistently keep track of the "probably up to date" set between
builds.

In this patch we just calculate and maintain these things but don't yet
use them except for debug output. The idea is it should be useful for
things like maintaining the .ghc.environment, deleting stale build dirs
or package registrations, maintaining exe wrapers/symlinks etc.

[ci skip]

Dedupe include dirs inherited from dependencies

Fail if null components

Reduce path lengths for temp package src and build dirs

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

Show Version returning "mkVersion [...]"

If you build a big number of packages, all with
the same extra -I flags, the flags get inherited
by the dependent packages and duplicated.
For big dependency trees it can exceed the
maximum command line length on some systems,
this happened to me with Linux and hoogle 5.

This patch decreases the redundancy by
dropping all but the first occurrence of
an include dir, preserving the semantics,
as they are processed left to right.

This is for paths under $dist/tmp/ where we unpack package source
tarballs and build them. This is for packages destined for the store.
The names of these tmp dirs don't matter since they're guaranteed to be
unique, so we only need short identifiers. So stop using full package
names, and put the build artifacts in their own dir, rather than using a
dist dir under the src dir.

Implement DNS-based mirror bootstrap protocol

The d36a2d7c commit was overzealous,
as it not only removed the obsolete GHC HEAD entry, but also the
non-GHC HEAD entry which was there on purpose.

Remove "allow_failures" from travis configuration

Per the comment at [1] it is no longer necessary.

[1] https://github.com/haskell/cabal/pull/3966#discussion_r82519000

Add CI target for building Cabal using Stack

Fix -Werror failure.

This way `cabal` can bootstrap secure repos even if the primary Hackage
instance is currently unreachable, as long as there's at least one
reachable and working secure mirror available.

NB: This new code-path is only used for the initial bootstrap. Once the
repository cache has been bootstrapped, its `mirrors.json` meta-data is
used instead.

See also https://github.com/well-typed/hackage-security/issues/171

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