Parse list fields in cabal config file

Add FGSectionDescrs so cabal.project sections can be parsed using Fie…

runParseResult reutrns NonEmpty PError

Issue 5977

Bump version to 3.1.0.0

cabal run works with Literate Haskell file

Issue 5775 seems to be fixed, let's see

Improve CabalFileSearchFailure messages

The original error constructors had zero extra information (for
debugginng) when triggered. The error message "NoCabalFileFound"
is simply not useful without further context.

All of the existing CabalFileSearchFailure constructors now include
a FilePath field.

This reverts commit a6fff366.

This reverts commit 7fec503a.

Treating globs like filenames was always illegitimate, but this code
was broken further by the addition of recursive globs.

I had a look around for other dubious code along these lines, and it
looks like this site is the only problematic one.

Fixes #6125.

Make `debug-info` >= 1 imply library/executable-stripping: False

* Fix `v2-repl` changing directory incorrectly.

* Add changelog entry

* Add haddocks

* Add check for GHC geq 7.6 (`-ghci-script` wasn't there yet)

Fixes #2702

If you enable `debug-info` then you also have to stop the libraries and
executables being stripped as otherwise the debug symbols are removed.

Prevent dependency on private library

show-build-info (lib:Cabal part)

Hannes Siebenhandl authored 6 years ago and Mikhail Glushenkov committed 5 years ago

This commit builds upon the work of cfraz89 and completes
the lib:Cabal part of the show-build-info feature.

Co-authored-by: Chris Fraser <cfraz89@gmail.com>

Ben Gamari authored 9 years ago and Mikhail Glushenkov committed 5 years ago

This allows users to get a JSON representation of various information
about how Cabal would go about building a package. The output of this
command is intended for external tools and therefore the format should
remain stable.

Unpack in existing directory if empty