* Add `cabal-version` 3.12

* Add test for #9331

- `cabal check`: Guard Paths_* behind `cabal-version: 3.12` or higher,
  “fail” and “succeed” tests.
- `cabal build`: Guard Paths_* behind `cabal-version: 3.12` or higher,
  “fail” test.

* Guard PackageInfo behind cabal-version ≥ 3.12

---------

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

* (cabal check) Add “Unknown OS” test

* (cabal check) Add “Unknown arch” test

* (cabal check) Add “Unknown compiler” test

* (cabal check) Add “Package versions” check

* (cabal check) Add “`-Werror`” test

* (cabal check) Add “-j[n]” test

* (cabal check) Add “Defer type errors” test

* (cabal check) Add “Debug flag” test

* (cabal check) Add “Profiling flag” test

* (cabal check) Add “Unused flag” test

* (cabal check) Add “Custom fields” check

* (cabal check) Add “Paths_module extension” test

* (cabal check) Add “Setup bounds” test

* (cabal check) Add “Duplicate module” test

* (cabal check) Add “No license” check

* (cabal check) Add “NONE license” test

* (cabal check) Add AllRightsReserved warning test

* (cabal check) Add “compatibility” license test

With cabal-version < 1.4, some license (e.g. ISC) mess up the
parser.

* (cabal check) Add “Unknown license” test

* (cabal check) Add “Suspicious BSD4” test

* (cabal check) Add “Suspicious version” test

* (cabal check) Add “`license-file` missing” test

* (cabal check) Add “Unrecognised repo type” test

* (cabal check) Add “No `type`” test

* (cabal test) Add “No `location`” test

* (cabal check) Add “No `module`” test

Only for CVS repos.

* (cabal check) Add “`tag` needed” test

For `this`-type source-repositories.

* (cabal check) Add “Relative path” test

* (cabal check) Add “Good relative path” test

* (cabal check) Add “ghc-options” test.

Checks if there is a tricky GHC option in `ghc-options`. We will
*not* write an integration test for each offending option, just
one (in this case for `-fasm`) to make sure the field is scanned.

* (cabal check) Add “ghc-shared-options” test.

Checks if there is a tricky GHC option in `ghc-shared-options`. We
will *not* write an integration test for each offending option, just
one (in this case for `-fglasgow-exts`) to make sure the field is
scanned.

* (cabal check) Add “ghc-prof-options” test.

Checks if there is a tricky GHC option in `ghc-prof-options`. We
will *not* write an integration test for each offending option,
just one (in this case for `-o`) to make sure the field is scanned.

* (cabal check) Add “`cc-options` include” test

* (cabal check) Add “Cxx `extra-libraries`” test

* (cabal check) Add “`cc-options` libdir” test

* (cabal check) Add `Cxx -Os` test.

* (cabal check) Add “Portable CPP flags” test

* (cabal check) Add “Invalid on Win” test

* (cabal check) Add “Outside relative path” test

Note that this test is not atomic; it comes with a "not a good
relative path" error, and this is unavoidable.

* (cabal check) Add “Absolute path” test.

Note that this test is not atomic; comes with a "not a good relative
path" *and* a "does not match any file" warning. This is unfortunately
unavoidable.

* (cabal check) Add “points to dist/” test

* (cabal check) Add “Testsuite ≥1.8” test

* (cabal check) Add “Default language” test

* (cabal check) Add “Default language spec” test

* (cabal check) Add “Extra doc” test

* (cabal check) Add “Multilib/namedlib” test

* (cabal check) Add “Reexported module” test

* (cabal check) Add “Mixins” test

* (cabal check) Add “Extra framework dirs” test

* (cabal check) Add “Default extensions” test

* (cabal check) Add `extensions` test

* (cabal check) Add Sources test

* (cabal check) Add “Extra libs” test

* (cabal check) Add “Virtual modules” test

* (cabal check) Add “Source repository” test

* (cabal check) Add “Extension break” test

* (cabal check) Add “Custom setup” test

* (cabal check) Add “Autogen modules” test

* (cabal check) Add “No z-prefixed check” test

* (cabal check) Add “No `build-type` specified” test

* (cabal check) Add “Ignoring custom-setup” test

* (cabal check) Add “Unknown compiler” test

In `tested-with`

* (cabal check) Add “Unknown language” test

* (cabal check) Add “Unknown extension” test

* (cabal check) Add “Language as extension” test

Languages cannot be listed in `default-extensions`.

* (cabal check) Add “Deprecated extension” test

* (cabal check) Add “No synopsis” test

* (cabal check) Add “No description” test

* (cabal check) Add “No category” test

* (cabal check) Add “No maintainer” test

* (cabal check) Add “Short description” test

`description` should be longer than `synopsis`.

* (cabal check) Add “Invalid tested with range” test

* (cabal check) Add “Internal library” test

On impossible version ranges for internal libraries.

* (cabal check) Add BOM test

* (cabal check) Add “Name mismatch” test

* (cabal check) Add “Missing .cabal” test

* (cabal check) Add “Missing license file” test

* (cabal check) Add “No setup file” test

* (cabal check) Add “No configure file” test

* (cabal check) Add “Local paths” check

* (cabal check) Add “Missing VCS info” test

* (cabal check) Add “Partial extension match” test

* (cabal check) Add “Filename too long” check

`signatures` field can be used only with `cabal-version` ≥ 2.0

quasicomputational authored 6 years ago and Alexis Williams committed 6 years ago

These globs make `haddock`, `sdist` and `install` die, so they
definitely ought to be warned about!

Because of the dying behaviour, I made the checks dist-inexcusable;
starting from a clean slate I would probably have only made them
suspicious, but this isn't terrible.

quasicomputational authored 6 years ago and Alexis Williams committed 6 years ago

This also significantly improves the error when trying to refer to
missing directories, hopefully making it clear that it's coming from
Cabal. #5318 and snowleopard/hadrian#634 are two bugs which manifested
as Cabal trying to glob in a non-existent directory and both took some
debugging because of the obscurity of the error.