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?

* bootstrap.py: fix incomplete reads when fetching from Hackage

fix #10998 

The fix was suggested by ChatGPT.

* fixup!

* fixup!

* fixup!

* fixup!

---------

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

Matthew Pickering authored 4 months ago and Mikolaj Konarski committed 4 months ago

- Removed 9.0.* plan
- Updated plans for 9.2.8, 9.4.8, 9.6.7, 9.8.4, 9.10.1, 9.12.2

Bumped the index state to get new enough versions to support 9.12.2.

Patching `cabal.release.project` still allows the buggy `unix`
release to be installed via Hackage.

* Make Cabal-hooks version track Cabal version

As pointed out in #10412, it isn't currently feasible to version the
Cabal-hooks version separately from Cabal due to the large amount of
re-exports (in particular the LocalBuildInfo type and its dependencies).

For the time being, we will version Cabal-hooks along with the major
Cabal library version.

* Update Cabal-hooks/changelog.md

- Avoid -Wname-shadowing
- Use -XDisambiguateRecordFields as needed
- Avoid -Wname-shadowing by importing qualified

* Bump version numbers to 3.15

* Bump GHC 9.6.6 for workflows

* Update index-state

* Bump bootstrap boundaries

* Regenerate bootstrap files

(cherry picked from commit aede6c4e)

Also remove 8.10.7 to match 3.12 branch.

Using the updated version of this library improves performance of
cabal-install so it's worthwhile to make sure the bootstrap plans use
this version.

We need to use the cabal.bootstrap.project file to generate the bootstrap plans, otherwise we try to include test components when bootstrapping, which is not useful (and significantly complicates bootstrapping).

- Rename cabal.bootstrap.project
- Rename cabal.meta.project
- Rename cabal.validate-libonly.project
- Rename cabal.validate.project
- Rename cabal.release.project

And add the relevant CI jobs for these plans

Fixes #8937.

The debug-conflict-sets build flag probably hasn't been used for a long time,
and it isn't currently tested. This commit removes the flag, converts the
ConflictSet type back to a newtype, and removes an unnecessary instance.

* Add alex to build-tool-depends and remove separate code gen

- Pass latin-1 encoding is passed as input pragma
- Cabal hard-codes -g for alex so we don't need to worry about --ghc
- Rework bootstrap, adding per-component building
- Update bootstrap plans

* [bootstrap] warn the user if cabal config is not found

* [bootstrap] regenerate bootstrap plans once more

* [bootstrap] regenerate bootstrap files after #9139

Matthew Pickering authored 2 years ago and Ben Gamari committed 2 years ago

* The top-level user interface to enable the use of the semaphore is the
  `--semaphore` flag. If you pass `-j4 --semaphore` then cabal will
  create a semaphore with 4 slots which is passed to ghc using the
  `-jsem` option so that all GHC processes coordinate to use 4
  capabilities.

  - The semaphore logic is provided by a new package `semaphore-compat`
    which provides a cross-platform abstraction for semaphores.

* The low level `./Setup.hs build` interface accepts the `--semaphore
  <SEMAPHORE>` option, which can be used to directly pass the semaphore
  you require to the Setup script.

* facelift bootstrap/README.md

* fixup! facelift bootstrap/README.md

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

* Update bootstrap/README.md

---------

Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Remove v2-prefix from other documentation where appropriate

* Added a changelog file

* Merge branch 'master' of github.com:haskell/cabal into remove-v2-from-docs

* Implemented PR feedback

* Reverted changes to regression tests

* Update CONTRIBUTING.md

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

* Update bootstrap/bootstrap.py

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

* Apply suggestions from code review

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

* Merge branch 'master' into remove-v2-from-docs

* Removed changelog entry

* Merge branch 'remove-v2-from-docs' of github.com:aspidites/cabal into remove-v2-from-docs

* Reverted bootstrap/README.md

* Merge branch 'master' into remove-v2-from-docs

Co-authored-by: ulysses4ever <6832600+ulysses4ever@users.noreply.github.com>

* 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>

I updated the dependencies in the .cabal bootstrap file and
sightly adjusted src/Main.hs for the `I.riCabal → I.riCabalHash`
change.

Fixes #8613

* Move towards using XDG directories.

* Install binaries in $HOME/.local/bin.

* Fix tests.

* Ensure config file is where it should be.

* Require newer directory for XdgState.

* Put world file in XDG_STATE_HOME.

* Oops, forgot to import.

* Remove uses of getCabalDir.

* These all need directory-1.3.7.0 now.

* Oh right, not a builtin anymore.

If this works I will also change the other .json files.

* Try it by hand.

* Haskell is better than JSON.

* Bump directory in all jsons.

* Put directory first.

* Let us assume that getConfigFilePath gets this right.

* Implement backwards compatibility.

* This is now elsewhere.

* We need to create parents as well because ~/.local might not exist.

* Put scripts-build in distinct cache directory.

* Document XDG behaviour.

* Remove help text references to ~/.cabal.

* Remove references to .cabla/bin.

* Backwards compatible install paths.

* Remove more references to ~/.cabal.

* Fix typo.

* Fix ~/.cabal paths making their way into default config.

* Reduce duplication.

* Add changelog entry.

* Also note install dir change.

* It is the cabal-install config file.

* Avoid dependending on cabal-install in Hackage-tests.

* ALso respect CABAL_DIR here.

* Try leaving InstallDirs alone.

* Also need duplication here.

* Add missing newline.

* Fix doc typos.

* Make this a Haddock comment.

* Revision field must not be null.

* Link directories.

* Update doc/config.rst

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

* No need for this.

* We install foreign libraries here now.

* Clarify Nothing case.

* Avoid using ~/.config/cabal in manual.

Co-authored-by: Mikolaj Konarski <mikolaj@well-typed.com>
Co-authored-by: Artem Pelenitsyn <a.pelenitsyn@gmail.com>

This ports to cabal-install the offline bootstrapping logic which was
introduced for Hadrian in GHC MR !6315.

This adds a "fetch" command to the bootstrap script, which fetches
all the dependency tarballs from Hackage, to be used in an offline
build. See bootstrap/README.md for further information.

Also polish README a bit.

This is guarded to be for GHC from 8.2 only, since the process release
depends on base-4.10.

Includes an update to the bootstrapping files.

- parametrize the bootstrap update Makefile target to make changing
  the list of GHC versions a bit easier
- add GHC 9.0.2 and 9.2.3 to the list of bootstrapping GHC versions
- regenerate the bootstrapping plans across all GHC versions

This allows bootstrapping against zlib 0.6.3.0, which ships
without Setup.hs.

I hope this should generally be a more robust approach than
asking maintainers of dependencies to keep Setup.hs.

- remove tee output
- disable debug logging in cabal-bootstrap-gen by default

This removes the need for passing dedicated project and build
directory names and cleans up the top level directory a little
bit.

Manually replayed from 45be9e44

This isn't currently a concrete problem, but surfaced when adding
a dependency to cabal-install:exe.