Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "no command line variant" for source-repository-package. #9975

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions doc/cabal-project-description-file.rst
Original file line number Diff line number Diff line change
Expand Up @@ -216,6 +216,14 @@ consider during package retrieval. This allows use of a package from a
remote version control system, rather than looking for that package in
Hackage.

Since version 3.4, cabal-install creates tarballs for each package coming from a
``source-repository-package`` stanza (effectively applying cabal sdists to such
packages). It gathers the names of the packages from the appropriate ``.cabal``
file in the version control repository, and allows their use just like Hackage
or locally defined packages.

There is no command line variant of this stanza.

.. code-block:: cabal

packages: .
Expand All @@ -237,12 +245,6 @@ Hackage.
tag: e76fdc753e660dfa615af6c8b6a2ad9ddf6afe70
post-checkout-command: autoreconf -i

Since version 3.4, cabal-install creates tarballs for each package coming
from a ``source-repository-package`` stanza (effectively applying cabal
sdists to such packages). It gathers the names of the packages from the
appropriate ``.cabal`` file in the version control repository, and allows
their use just like Hackage or locally defined packages.

.. _source-repository-package-fields:

The :ref:`VCS fields<vcs-fields>` of ``source-repository-package`` are:
Expand Down
Loading