testuite: doctest: move to ghcup-recommended ghc

* Fix cabal init should not suggest Cabal < 2.0

* Remove + symbol cabal-version 2.0

elim warning spam from #8500

* Fix cli list parse errors in `cabal init`

Occurrences of `Flag [a]` behave in a slightly unexpected way. The monoid
instance of `Flag` is right associative and discard the value on the
left.
Thus, make sure we merge the contents of the flags, instead of using the
monoid instance of `Flag` itself.

* Document fixes and improvements

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

* cabal check: Warn if expected files are omitted from extra-doc-files

* Add test

* Add missing files and their hackage’s reference

* Move doc file check from checkPackageContent to checkPackageFilesPreDistribution

* Check based on globs only

Check only globs, not the filesystem.

* Update test outputs

* Make check more robust to relative paths

* Fix tests failing with "Distribution quality warnings"

* Fix comments and changelog [skip ci]

* Test changelog only if present

* Revert "Update test outputs"

This reverts commit ce49487d804691f77aff38b89449c2d0f09dbd44.

* Revert "Fix tests failing with "Distribution quality warnings""

This reverts commit 705f6bd0144057f5c1d375f9eceb90645b218a88.

* Fix changelog

* Remove getGlobFiles

* Adapt warnings to version 1.12

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

Fix #8664 redux: add EOL character to list-bin output

* Add support for js-sources

* Add changelog

* Add comment about C-like sources

* Add tests

* Fix test

* Fix skipUnless and factorize

* Fix skipIfGhcVersion

Bump known ghc versions in cabal library to < 9.8

* Remove unused binding

* Add failing test

* Resolve import from relative paths within cabal.project

* Add expected test output

* Add changelog

* Remove unused imports

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

Fix build instructions in CONTRIBUTING.md for people with old cabal

Add support for the -fprof-late flag new in 9.4

TargetSelector: Include a hint in the error message for internal error

This is a mediocre solution, and really should generate a different
error entirely at an earlier stage, but I'm not familiar enough with how
to achieve that.

* Add check for recursive glob in root directory

Such globs might be expensive to include, as they might pull unnecessary
 directories just like `.git` or `dist-newstyle`.

* Move expensive glob warning to its own constructor

* Add changelog entry

* Add test for recursive glob warning

* Fix formatting

cabal-testsuite #8401: communicate better the need for `--with-cabal`

- Add caveat to `--help` text.
- Put `--with-cabal` into very first example in README.

Rather than obfuscating by sprinkling in a fully qualified reference
to `<>` when unqualified references also work, limit the import of
`Data.Monoid.<>` with a suitable CPP.

* Fix #8400 by marking output of `cabal list-bin`

The regular output of `cabal list-bin` should go to stdout always, but
be marked for the sake of the testsuite.

* Make test Windows-compatible

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

Re #6125: document that glob dirs are buggy in Cabal 2.4

`cabal-version: 2.4` allows e.g. `data-files: foo/**/*.txt` but `**`
directories are only handled correctly since Cabal 3.0 (issue #6125).
This information should be part of the cabal file format history
documentation.

Add since pragma for ppOrdering

* prepend rather than append extra prog path

* changelog

* test

* skip on windows

* update test

* fix test

* reenable windows skip

* Update setup.test.hs

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

* don't send non-extant extra-lib-dirs to ghc #6492

* changelog

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

* Add changelog entry

* Add test

* Remove "'-main-is' is not portable" check

* Fix test

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

* Fix #8654: no assertion warning on special modes (help, version, etc.)

This patch moves the `warnIfAssertionsAreEnabled` until after the main
command line argument parsing, and then only prints it on regular
operation, i.e. not when just the help or version of cabal was
demanded, or the command line could not be parsed.

Further, the warning is printed on stderr.  The previous attempt to
use `warn` does not work as expected, as the verbosity aperatshnik
isn't in place yet, so the warning cannot be suppressed by -v0.

Drive-by-shooting: straighten the convoluted control flow involving
`maybeScriptAndArgs`.  This IO computation was invoked "brutto"
before, when it is actually only needed in *one* branch of the case
distinction.

* PR #8647: changelog, fix text of warning

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

* don't create a cache directory when the compiler isn't configured

* Update pr-8358

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

* improve install target handling logic

* changelog

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

Fix typo in cabal.test.hs

suport -> support

Tiny refactor of how Cabal handles configure scripts