GitLab

This reverts commit bacdf19b.

'hackage-security' has been updated. I tested that build works now.

hackage-security hasn't been updated with new bounds, so this
unbreaks the build.

This reverts commit eec15a35.

kristenk authored Jan 29, 2017 and Edward Z. Yang committed Feb 03, 2017

For example, "setup.Cabal installed" forces cabal to use the installed Cabal
library for all setup scripts.

kristenk authored Jan 29, 2017 and Edward Z. Yang committed Feb 03, 2017

For example, --constraint="any.pkg == 5" applies to "pkg" whether it is a
top-level dependency, setup dependency, or build tool dependency.

I also modified the UserConstraint type so that it is more similar to the
PackageConstraint type, now that both types need to express similar
"constraint scopes".

Mikhail Glushenkov authored Jan 11, 2017 and Mikhail Glushenkov committed Jan 17, 2017

[ci skip]

[ci skip]

[ci skip]

[skip ci]

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

[ci skip]

Fixes #2214 by adding a `reconfigure` command and invoking it whenever
necessary. The last configure flags used are saved in a
version-independent format so it should never be necessary for the user
to reconfigure manually.

Specifically, this changes the default from `.../$pkgid.log`
to `.../$compiler/$libname.log`, which avoids logfiles overwriting
each other even though theyty refer to different artifacts, as well
as aligning the format with `~/.cabal/store`'s structure.

This addresses #3807

[ci skip]

Removing 'topdown' as a resolver choice means that 'choose' is also
obsolete and so it is removed too.

[ci skip]

Fixes #1823.

Pkg-config constraints are actually a part of 1.24.

[ci skip]

(cherry picked from commit 9cd1387fcd582a6131746e6742597069d54f905a)

[ci skip]

Fixes #2756.

* Renamed to 'extra-framework-dirs'.
* Added 'extra-framework-dirs' to ConfigFlags.
* Added some checks.
* Updated changelog.

* Fix parsing of '--allow-newer=foo --allow-newer=bar'.
* Fix './Setup configure --allow-newer --enable-{tests, benchmarks}'.

Tomas Vestelind authored May 30, 2015 and Mikhail Glushenkov committed Jan 31, 2016

'cabal user-config init' creates a default config file if it doesn't already
exist.

If '--config-file' is set, then that file will be written.

If '-f' or '--force' is used, then the file will be overwritten if it already
exists.