* Give an example for `--enable-nix` flag

* fixup! Give an example for `--enable-nix` flag

* fixup! Give an example for `--enable-nix` flag

* Add `cabal get` documentation

* Add `cabal upload` documentation

* Add `cabal info` documentation

* Add `cabal fetch` documentation

* Add `cabal init` documentation stub

* Add `cabal list` documentation

* Add `cabal report` documentation

* Add `cabal user-config` documentation

* Add changelog for #8309

* Document alternatives to `cabal fetch`

* Warn about packages default value

* Use double backquotes

* Syntax correction

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

* Implement --prefer-oldest

* Test --prefer-oldest

* Add changelog for --prefer-oldest

* Add documentation for --prefer-oldest

* Review suggestions

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

With this option, 'cabal get' writes to the destination directory only the
package description already available locally in one of the repository
indices.

The basename of the file name written to inside the target directory is
the package-id rather than only the package name.

This is mostly based on #1977

Co-authored-by: Miëtek Bak <mietek@bak.io>
Co-authored-by: Artem Pelenitsyn <a.pelenitsyn@gmail.com>

Co-authored-by: Herbert Valerio Riedel <hvr@gnu.org>
Co-authored-by: Miëtek Bak <mietek@bak.io>

fix warnings: update extlinks format to Sphinx 5

There was nothing about installing packages in this file for a while now.

Use proper option formatting instead of bullet points.

Vilius Panevėžys authored 2 years ago and Mikolaj Konarski committed 2 years ago

The package counts have grown to 15353 and 43351 respectively as of this
writing, hence the ratio has dropped from 5.6 to 2.8. Given the growth
of Hackage, the comparison does not seem as important anymore (does it
matter if you have 3 or 8 alternative libraries for the same purpose?).
Dropping package counts to avoid the need for continuous updates.

It was a bit surprising to me that `cabal list-bin foo` prints a path
to an executable `foo` that may not actually exist.

+ Update file-format-changelog.rst

The original Cabal proposal https://www.haskell.org/cabal/proposal/ explained that `runhaskell`, in the proposal, was to refer to a symlink to `runhugs`, `runghc`, or `runnhc`. That explanation has been lost from the Cabal guide. Since the date of the original proposal, HUGS and NHC have fallen by the wayside. This pull request proposes two minor additions to restore the explanation:

1. A sentence "GHC provides the commands `runhaskell` and `runghc` (they are equivalent) to allow you to run Haskell programs without first having to compile them (scripts)." This wording closely follows that in the GHC user guide.

2. A clarification that `--help` provides information about the `Setup.hs` script (not the `runhaskell` command).

Document only v2-haddock option syntax.

The command-line syntax given was for `cabal v1-haddock`.
Now, there is both the command-line syntax for `cabal haddock` and
`cabal v1-haddock`.

Furhter, add missing field: `haddock-quickjump`.

Resolves #7459

This commit adds entries for the 'gen-bounds' and 'outdated'
commands to the "cabal-install Commands" section of the user manual.

Formerly, those commands were only described in the "Package
description" section. Some, but not all, of the information in that
section has been moved to the entires in the list of commands.

This commit changes two other things:

- The descriptions in the "Package description" were incorrectly placed
  as sub-sections of "Opening an interpreter session". They have been
  moved one level up.

- changed the gen-bounds example, because it used dependencies which
  *already* had bounds as the starting point.

Co-authored-by: Daniel Díaz <diaz_carrete@yahoo.com>
Co-authored-by: Emily Pillmore <emilypi@cohomolo.gy>
Co-authored-by: gbaz <gershomb@gmail.com>

* allow glob matches of the form dir/**/FileNoExtension

* allow glob matches of the form dir/**/FileNoExtension

* tests, docs, changelong

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

* initial parser pass

* first compiling pass

* get more stuff sort of working

* conditional parsing actually works

* error cleanup and downloads

* thread through http transport

* fix merge

* better errors and use extended project parsing uniformly

* elif support, maybe?

* fix outdated cmd, add tests, docs

* fix docs

* use legacyReadFields parser

* changelog

* cyclical import detection

* fix shadowing

* add missing file

* finish merge

* fix outstanding merge issue

* use existing config available when checking for compiler for package flags

* review comments

* add missing test file

* Update pr-7783

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