Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
C
Cabal
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Locked Files
Requirements
Requirements
List
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Security & Compliance
Security & Compliance
Dependency List
License Compliance
Operations
Operations
Environments
Packages & Registries
Packages & Registries
Package Registry
Container Registry
Analytics
Analytics
CI / CD
Insights
Issue
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Jobs
Commits
Open sidebar
Glasgow Haskell Compiler
Packages
Cabal
Commits
05ec12fe
Commit
05ec12fe
authored
Dec 04, 2018
by
Oleg Grenrus
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add notes about spec 3.0 changes [skip ci]
parent
d60f3a50
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
22 additions
and
4 deletions
+22
-4
Cabal/doc/developing-packages.rst
Cabal/doc/developing-packages.rst
+5
-4
Cabal/doc/file-format-changelog.rst
Cabal/doc/file-format-changelog.rst
+17
-0
No files found.
Cabal/doc/developing-packages.rst
View file @
05ec12fe
...
...
@@ -1260,7 +1260,7 @@ The library section should contain the following fields:
`signature thinning
<https://wiki.haskell.org/Module_signature#How_to_use_a_signature_package>`__.
The library section may also contain build information fields (see the
section on `build information`_).
...
...
@@ -2219,7 +2219,7 @@ system-dependent values for these fields.
so for Nix-style builds. Specifically:
a) For Nix-style local builds, both internal and external dependencies.
b) For old-style builds, only for internal dependencies [#old-style-build-tool-depends]_.
b) For old-style builds, only for internal dependencies [#old-style-build-tool-depends]_.
It'
s
up
to
the
user
to
provide
needed
executables
in
this
case
under
`$
PATH
.`
...
...
@@ -2612,7 +2612,7 @@ system-dependent values for these fields.
the
names
of
the
signature
and
of
the
implementation
are
already
the
same
,
the
matching
is
automatic
.
But
when
the
names
don
't coincide, or we want to
instantiate a signature in two different ways, adding mixin entries that
perform renamings becomes necessary.
perform renamings becomes necessary.
.. Warning::
...
...
@@ -3002,7 +3002,8 @@ Starting with Cabal-2.2 it's possible to use common build info stanzas.
- You can import multiple stanzas at once. Stanza names must be separated by commas.
- ``import`` must be the first field in a section.
- ``import`` must be the first field in a section. Since Cabal 3.0 imports
are also allowed inside conditionals.
.. Note::
...
...
Cabal/doc/file-format-changelog.rst
View file @
05ec12fe
...
...
@@ -32,6 +32,23 @@ relative to the respective preceding *published* version.
* Remove deprecated ``hs-source-dir``, :pkg-field:`extensions` and
:pkg-field:`build-tools` fields.
* Common stanzas are now allowed also in the beginnning of conditional
sections. In other words, the following is valid
::
library
import deps
if flag(foo)
import foo-deps
* Allow redundant leading or trailing commas in package fields with
optional commas, such as :pkg-field:`exposed-modules`
* Require fields with optional commas to consistently omit or place
commas between elements.
``cabal-version: 2.4``
----------------------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment