[ci skip]

Add dependency-graph information to `printPlan` output

Herbert Valerio Riedel authored 9 years ago and Mikhail Glushenkov committed 9 years ago

This improves the install-plan reporting in `cabal install -v2`'s output
to include reverse-dependencies, thereby giving valuable information why
a package was included in the install-plan to begin with.

Moreover, this also disables line-wrapping for the install-plan for
verbosity `verbose` and greater, to make the output easier to parse
for humans as well as computers

Example output for `cabal install --dry -v2 http-client`:

  In order, the following would be installed:
  base64-bytestring-1.0.0.1 (via: http-client-0.4.11.2) (new package)
  data-default-class-0.0.1 (via: http-client-0.4.11.2 cookie-0.4.1.5) (new package)
  mtl-2.2.1 (via: exceptions-0.8.0.2 parsec-3.1.9) (new package)
  network-2.6.0.2 (via: http-client-0.4.11.2 streaming-commons-0.1.12) (new package)
  old-locale-1.0.0.7 (via: cookie-0.4.1.5) (new package)
  random-1.1 (via: http-client-0.4.11.2 streaming-commons-0.1.12) (new package)
  stm-2.4.4 (via: streaming-commons-0.1.12 exceptions-0.8.0.2) (new package)
  text-1.2.0.4 -integer-simple (via: http-client-0.4.11.2 streaming-commons-0.1.12 parsec-3.1.9 mime-types-0.1.0.6 http-types-0.8.6 case-insensitive-1.2.0.4 hashable-1.2.3.2 cookie-0.4.1.5 blaze-builder-0.4.0.1) (new package)
  blaze-builder-0.4.0.1 (via: http-client-0.4.11.2 streaming-commons-0.1.12 http-types-0.8.6 cookie-0.4.1.5) (new package)
  cookie-0.4.1.5 (via: http-client-0.4.11.2) (new package)
  hashable-1.2.3.2 (via: case-insensitive-1.2.0.4) (new package)
  case-insensitive-1.2.0.4 (via: http-client-0.4.11.2 http-types-0.8.6) (new package)
  http-types-0.8.6 (via: http-client-0.4.11.2) (new package)
  mime-types-0.1.0.6 (via: http-client-0.4.11.2) (new package)
  parsec-3.1.9 (via: network-uri-2.6.0.1) (new package)
  network-uri-2.6.0.1 (via: http-client-0.4.11.2) (new package)
  transformers-compat-0.4.0.4 (via: exceptions-0.8.0.2) (new package)
  exceptions-0.8.0.2 (via: http-client-0.4.11.2) (new package)
  zlib-0.6.1.0 (via: streaming-commons-0.1.12) (new package)
  streaming-commons-0.1.12 (via: http-client-0.4.11.2) (new package)
  http-client-0.4.11.2 (new package)

(cherry picked from commit c0b3c7f1)

Fixes #3054.

bootstrap.sh: add missing pkg and fix tar position

* tar needs to be installed before hackage-security
* base64-bytestring is also required

allow building with recent (master) HTTP

I need it for GHC 8 support

Distribution.Simple.GHC: minor improvements

Tests for #2731 (Ignore dependencies that are not Buildable)

'DSL.exResolve' now takes a 'Maybe [Extension]' for supported extensions and
a 'Maybe [Language]' for supported languages.  'Nothing' means that
extensions/languages are not checked by the solver, and 'Just []' means that
no extensions/languages are allowed.

Andres Löh authored 9 years ago and kristenk committed 9 years ago

When configuring a package, the condition trees in the package
descriptions are evaluated according to the known configuration
and flag assignment.

During this process, it becomes also known whether a component
has its "Buildable" flag set to True or False. We now disregard
all dependencies of non-buildable components.

Andres Löh authored 9 years ago and kristenk committed 9 years ago

When doing the index conversion prior to dependency solving, we now
consider the "Buildable" flag for package components.  In particular, if
the "Buildable" flag of a component is "True" only under certain
conditions, then all build dependencies of that component will be placed
under the same conditions.

First stab at documenting repo configuration

Tweak the GHC-8 / binary-0.8 version CPP hackery

Try and pick the right default for ghc-8.

Introduce secure repos

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

Remove dead code in modular solver

Introduce RepoContext

don't special-case versions with leading zeroes

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

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

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

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

Cabal's LibV09 support has always been a bit skeevy.  The general
idea was that a detailed-0.9 test-suite is built as a library
and an Cabal-provided stub executable.  In particular, the test suite
library must be installed to the installed package database so that the
executable can be compiled.

Old versions of Cabal did something very skeevy here:  they installed
the test library as a "package", with the same package name as
the "test-suite" stanza; furthermore, they built the products
into the same directory as the library proper.

Consequently, a lot of bad things could happen (both of which I've
added tests for):

    1. If the name of the test suite and the name of some other
    package coincide (and have the same version), they will clobber
    each other.  In GHC 7.8 and earlier, this just flat out
    kills the build, because it will shadow.  There's an explicit
    test to make sure test suites don't conflict with the package
    name, but you can get unlucky.

    2. The test suite library is built into the same directory
    as the main library, which means that if the test library
    implements the same module name as something in the main
    library it will clobber the interface file and badness
    will ensue.

This patchset fixes both of these issues, by (1) giving internal
test libraries proper names which are guaranteed to be unique
up to Cabal's dependency resolution, and (2) building the test
suite library into a separate directory.

In doing so, it also lays the groundwork for other types of
internal libraries, e.g. #269, as well as extra (invisible)
libraries which we may install.

For GHC 7.8 and earlier, we follow the reserved namespace
convention as per #3017.

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

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