GitLab

Add LibraryVisibility to InstalledPackageInfo

This patch only modifies the datatype. The field is not filled with the
correct visibility info yet.
A ghc-pkg compiled with this patch is needed to actually record this
information and properly test the visibility checks.

Add `--lib`, `--exe`, and `--libandexe` shorthands to cabal init.

Add runParsecParser', which takes CabalSpecVersion

Use FieldName in FieldGrammar.FieldDescrs

Add showFields-prime

Introduce Distribution.Fields module namespace

Split fields related functionality out of `Distribution.Parsec`
namespace which is not left only to handle "scalar" values.
This separation highlights that we use `parsec` for *structure* (think
JSON), and the *values* of the fields (think e.g. dates in JSON).

- New top-level `Distribution.Fields` and `Distribution.Parsec` modules
  should include most things most people would need.
- Also `Distribution.Pretty.Field` is moved to `Distribution.Fields.Pretty`,
  as now it has proper place.
- The commit is moving things around and fixing compilation errors.
- I fixed `cabal check` parse error printing as I was nearby.

Add rules to run tests via "make parser-tests" etc

Add hacked the --cwd argument parsing to
parser-tests and check-tests. It's a kludge
but it's good enough.

Make hackage-tests parallel. Resolves #5736

[ci skip]

Solver: Improve error message by finding a minimal conflict set (issue #5647).

Fix `--with-compiler` failing to locate compiler on Windows

pass --host=$HOST to configure when cross-compiling

Make v2-test succeed when no test suites found

Automatically pass -x to hsc2hs when cross-compiling

This changes the default behaviour to succeed when no test suites are found. The
old behaviour can be achieved by passing --test-fail-when-no-test-suites.

Sessions with new changes:

$ cabal v2-test
Resolving dependencies...
No tests to run for the package initsample-0.1.0.0

$ cabal v2-test --test-fail-when-no-test-suites
Resolving dependencies...
cabal: Cannot run tests for the target '' which refers to the package
initsample-0.1.0.0 because it does not contain any test suites.

Sometimes, rerunning the solver to remove one variable from the conflict set
also removes other variables.  This commit checks whether each variable is still
present in the conflict set before trying to remove it, which can save expensive
solver reruns.

Minimizing the conflict set requires rerunning the solver multiple times, which
can be time consuming.  This commit adds a flag, --minimize-conflict-set, that
defaults to false.  We should probably add a way to limit the total run time
before turning the feature on by default, such as applying the backjump limit to
the combined solver runs.