GitLab

This reverts commit 9d217525.

I don't know where that 'let' came from :-/

Make store path absolute

`cabal init` needs a haskell compiler to operate but is missing the `-w` flag 
other commands have (see also #4956). This patch addresses this inconsistency.

Fixes #5654
Fixes #4936 

Relative --storedir paths caused ghc-pkg failures.

Fixes #5485

[GSoC2018] Add support for multiple public libraries in a single package

When this flag is active we only execute the Cabal build system's 'configure'
step for each local unit and nothing else. This allows (re)generating the Setup
configuration cache which is accessed directly by tooling like ghc-mod and HIE
through cabal-helper and allows such tooling to forgoe a full rebuild.

This allows us to request only a configure step be run for a given unit.

This reverts commit 1c4ad06c4490125ee43ae4d8fe66a8dde95aa8c7.

The previous commit fixed it

We generated them both the old way (only internal libs) and the new way
(arbitrary sublibraries), leading to this:

    $ cabal new-configure my-package -v
    [...]
    Component graph for my-package-0.2.0.0: component exe:my-exe
    component my-package-0.2.0.0-inplace-my-exe
        include base-4.11.1.0
        include base-4.11.1.0
        include word8-0.1.3-968d6922e82a4ae480d10bc205e047a27af7804ae8fb577c4b6eeb868f99ee3b
        include word8-0.1.3-968d6922e82a4ae480d10bc205e047a27af7804ae8fb577c4b6eeb868f99ee3b
    [...]

...which didn't have any effect on the build except for some duplicate
output, but could lead to problems in the future.

Now we only generate them the new way.

Dependency is used in two seemingly related but now incompatible ways:

* As a dependency specification ("I want this component from this package,
  version range xy")
* As a constraint ("Package p must be in version range xy")

This commit begins to separate the two concepts.

Create a new syntax for depending on any library of any package.
The syntax is

    build-depends: pkgname:{pkgname, sublibname} -any

where the second `pkgname` specifies a dependency on the main unnamed
library.

Closes #4206.

This gives us more type safety when dealing with libraries only

Before, a 3-tuple was used

The old --dependency could only do --dependency=pkg=cid,
but with public sublibraries this will become insufficient.

Now there is the option to also specify a component name using
--dependency=pkg:component=cid

Filter out ambiguous builddir flag

Check early for failures in new-install

Cabal: Allow time-1.9
(cherry picked from commit fa194aca)

So we don't try to symlink failed packages

Fixes #5550 (the dead symlink part, not the error reporting (#5641))

It conflicted with the flag with the same name from configFlags

Fixes #5550

new-install: error on existing symlink, overwrite option

[ci skip]

Fix monolithic inplace build tool PATH

Monolithic inplace packages have a directory for each exe, so we allow
multiple paths and return all the exe paths of the package.

Fixes #5104

Before, new-install could exit successfully while actually _not_ symlinking
anything.
Moreover, without an overwrite option, upgrading cabal was impossible
without moving links around.

* Error out on overwrite
* Overwrite if --force-overwrite is passed

Add DerivingVia to KnownExtensions