As the case of `cpphs-1.20.8` has shown in #5379, in cases when a
monolithic package gets installed due to its executable components
(i.e. `exe:cpphs`) into the store we *have* to register if there's a
buildable public library (i.e. `lib:cpphs`) that was built and installed
into the same store folder as otherwise this will cause build failures
once a target actually depends on `lib:cpphs`

This ought to fix #5379

Update travis: +8.6.3 +8.4.4 -8.4.3

See #5625. Somewhat experimental.

mbieleck authored 6 years ago and Edward Z. Yang committed 6 years ago

For some reason repl invocation was skipped for indefinite components.
However, GHCi seems to handle them just fine.

Fixes #5619.

Using the Unix epoch is causing problems on Windows because it's
before MS-DOS's epoch of 1980-01-01. Picking a different, memorable
one ought to solve that.

Closes #5596.

Datadir env var generation for vcs and tarballs

Fixes #5469

Check existence of packagedb before dumping it

If the pkgdb does not exist, skip it and treat it as an empty one

Fixes #5516

doc: common stanzas: import must be the first field

Fix a typo in cabal-install/bootstrap.sh [ci skip]

This adds support to `cabal init` for selecting the Cabal spec
version (i.e. the `cabal-version:` field) and also takes care
of translating between pre-SPDX and SPDX license ids.

Warn when failing to symlink an exe in new-install

This provides a partial fix/improvement to #5491

Does not warn if the existing symlink already points to the correct location

Partial solution to #5491

Filter out executables from package-id flags

Remove Text from D.Simple

- Add Parsec/Pretty CompilerId instances
- Fix Parsec PackageIdentifier instance (hopefully it wasn't used for
  anything important)

In the course of 4466310e (see #5526) the
`Setup.hs haddock` CLI was extended to allow component ids to be passed
as positional arguments. However, `autoconfUserHooks` which is used in
case of `build-type: Configure` wasn't updated accordingly, and consequently
this caused `new-haddock` to break for packages using `Configure`.

cc @alexbiehl

Fixes #5503

cc @phadej

Instead of directly committing binaries to GitHub (GitHub doesn't like them)
upload to Amazon S3. Any S3 bucket controlled by s3-bouncer
is acceptable; we have hardcoded s3-bouncer.heroku.com.
More info about s3-bouncer available at:
https://github.com/ezyang/s3-bouncer



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

and clean up various aspects related to the `cabal-version` field

Fix #5541.