GitLab

Freeze solver goal order in two more unit tests

Count conflicts to speed up solver

(It already was the default for install.)

cabal-install: make user config optional if possible

Fixes #3494.

Add a goal order parameter to the dependency solver

Update stack.yaml

Fix issue 3460: avoid concurrent package db creation

Instead initialise all the ones we'll need in advance of building any
packages. The alternative would have been to use a lock, but there's no
particular advantage in trying to delay initialisation and avoiding
locks keeps things simpler.

This should fix #3460

Another similar issue was fixed by 1acc00f8 which serialised the
registration of packages in the local inplace package db, avoiding
lost updates (which could previously be observed in test case T3460).

Edward Z. Yang authored Jun 06, 2016 and Duncan Coutts committed Jun 26, 2016

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

New freeze command

This is ok, but not perfect since freezing is now more tricky with setup
deps. See https://github.com/haskell/cabal/issues/3502

Code to write it and to pick it up by default when reading the
cabal.project file.

There are various related properties here like packages that are going
to be built locally inplace rather than added to the store, but
sometimes we need to know if a package was originally specified by the
cabal.project file (explicitly or implicitly).

It takes a solver plan, makes an "elaborated plan" with nix style hashes
but still of mostly source package and then does an improvement phase to
make a plan with pre-existing packages from the store.

Previously it only returned the improved plan, but for some things it's
also useful to see the original elaborated plan with the source
packages. In partciular it will be useful for plan.json status output.
It will also be needed for the freeze command to be able to get at the
flag choices, since this info is not preserved in installed packages.

byorgey authored Jun 17, 2016 and Mikhail Glushenkov committed Jun 23, 2016

Only those modules found in a directory in hs-source-dirs will be added
to exposed-modules.  If a directory 'src' is found it will be used as
hs-source-dirs (note in this case any .hs files in the root directory
will NOT be added to exposed-modules).  If any directories are specified
on the command line with --source-dir, they will be used.  If no
directories are specified on the command line and there is no directory
named src, the root directory will be used.

Fixes #3484.

Change install lock to just a registration lock

Exit with non-0 code when build fails

Fixes issue #3495

This also adds a stub where we can add more detailed failure reporting,
but this starts with nothing more than the exit code.

Unlike the existing "cabal install" failure reporting, we don't need or
want "build" failure reporting to be quite so noisy in common cases like
the one local package failing to build, since ghc reports its own errors
and there's enough context to see what's going on.