also update bootstraps for new hackage-security, and move splitmix
constraint to where it will work for more than just validate

also updated bootstrap to use ghc 9.10.2, which was missed earlier?

Bodigrim authored 3 months ago and Mikolaj Konarski committed 2 months ago

As http://www.haskell.org/pipermail/cabal-devel/2007-December/001509.html
explains, `Data.Monoid.Last` was introduced only in base-3.0 and was too
new in 2007 to rely on. Thus a compatibility shim `data Flag a` was
vendored in.

We are long past 2007 and `Data.Monoid.Last` can now be used instead.
The commit keeps providing `Flag` and `NoFlag` as pattern synonyms
for backward compatibility, but makes `type Flag = Last.`

- Use newer warning flags in Paths_pkg template
- Use newer warning flags in **/Z.hs

- Remove redundant -XCPP from Cabal-tree-diff
- Remove redundant -XCPP from cabal-install
- Remove redundant -XCPP from Cabal
- Remove redundant -XCPP from Cabal-QuickCheck
- Remove redundant -XCPP from Cabal-syntax
- Remove redundant -XCPP from Cabal-tests
- Remove redundant -XCPP from cabal-testsuite

* Bump version numbers to 3.15

* Bump GHC 9.6.6 for workflows

* Update index-state

* Bump bootstrap boundaries

* Regenerate bootstrap files

This commit makes the library functions in Cabal agnostic of the working
directory. In practice, this means that we distinguish `FilePath`s
from un-interpreted `SymbolicPath`s. The latter may be paths that are
relative to the working directory, and need to be interpreted with
respect to a passed-in argument specifying the working directory,
instead of using the working directory of the current process.
See Note [Symbolic paths] in Distribution.Utils.Path.

In particular, paths in the package description now use the SymbolicPath
abstraction, which allows specifying whether they are allowed to be
absolute, and, if they are relative, what they are relative to.
For example, source files are relative to a source search directory,
data files are relative to the data directory, and doc files are
relative to the package root.

Fixes #9702

* Bump versions on master branch to 3.11

* Try to fix CI by setting cabal-testsuite stable Cabal version to 3.8 back again

* Update bootstrap configuration

* Work around bounds problem with cabal-install-parsers

* Update bootstrap files

* Try to update the Custom setup cabal to 3.10 according to Artem's suggestion

* CI: cabal-3.10 compat: actions/cache has to go before cabal update

* Fix failing old GHC CI builds by adding XDG's ~/.local/bin to GITHUB_PATH

---------

Co-authored-by: Artem Pelenitsyn <a.pelenitsyn@gmail.com>

* handle datadir flag in newbuild

* fixup

* exclude installDirs options from cabal install

* fix tests

* changelong

Co-authored-by: Gershom Bazerman <gershom@arista.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Hannes Siebenhandl authored 3 years ago and Daniel Gröber (dxld) committed 3 years ago

Removes 'show-build-info' command from 'lib:Cabal' and replaces it
by generating build-info whenever a build happens.

Add flag '--dump-buildinfo' to signal the build step to dump
build information for the package/component we are currently building.

- regenerate bootstrap plans
- update CI and docker images for 8.8.4 and 8.10.4

The are various motivation points:
- I'm not aware anyone third party running Cabal tests (maybe nixpkgs?)
- No need to do gen-extra-source-files, as Cabal-tests is not distributed
- No multiple rebuilds of Cabal-QuickCheck, Cabal-tree-diff
- Slightly smaller Cabal sdist (which is quite big still)