Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 6bd55c0

Browse files
authoredMay 15, 2021
doc: Add anchors to dhall sections
This will ensure the sections have stable links as well as prevent conflicts (pandoc uses heading text for ids and DocBook requires unique ids across the book).
1 parent 0416cb2 commit 6bd55c0

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed
 

‎doc/languages-frameworks/dhall.section.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ support for importing Dhall expressions, which is documented here:
55

66
* [`dhall-lang.org` - Installing packages](https://docs.dhall-lang.org/tutorials/Language-Tour.html#installing-packages)
77

8-
## Remote imports
8+
## Remote imports {#ssec-dhall-remote-imports}
99

1010
Nixpkgs bypasses Dhall's support for remote imports using Dhall's
1111
semantic integrity checks. Specifically, any Dhall import can be protected by
@@ -32,7 +32,7 @@ example, the Prelude Dhall package uses `pkgs.fetchFromGitHub` to fetch the
3232
to fetch Dhall code ensures that Dhall packages built using Nix remain pure and
3333
also behave well when built within a sandbox.
3434

35-
## Packaging a Dhall expression from scratch
35+
## Packaging a Dhall expression from scratch {#ssec-dhall-packaging-expression}
3636

3737
We can illustrate how Nixpkgs integrates Dhall by beginning from the following
3838
trivial Dhall expression with one dependency (the Prelude):
@@ -117,7 +117,7 @@ in
117117
$ nix build --file ./example.nix dhallPackages.true
118118
```
119119

120-
## Contents of a Dhall package
120+
## Contents of a Dhall package {#ssec-dhall-package-contents}
121121

122122
The above package produces the following directory tree:
123123

@@ -224,7 +224,7 @@ $ cat ./result/source.dhall
224224
225225
```
226226
227-
## Packaging functions
227+
## Packaging functions {#ssec-dhall-packaging-functions}
228228
229229
We already saw an example of using `buildDhallPackage` to create a Dhall
230230
package from a single file, but most Dhall packages consist of more than one
@@ -297,7 +297,7 @@ terms of `buildDhallPackage` that accepts the following arguments:
297297
Additionally, `buildDhallGitHubPackage` accepts the same arguments as
298298
`fetchFromGitHub`, such as `sha256` or `fetchSubmodules`.
299299
300-
## `dhall-to-nixpkgs`
300+
## `dhall-to-nixpkgs` {#ssec-dhall-dhall-to-nixpkgs}
301301
302302
You can use the `dhall-to-nixpkgs` command-line utility to automate
303303
packaging Dhall code. For example:
@@ -342,7 +342,7 @@ $ dhall-to-nixpkgs directory ~/proj/dhall-semver
342342
}
343343
```
344344
345-
## Overriding dependency versions
345+
## Overriding dependency versions {#ssec-dhall-overriding-dependency-versions}
346346
347347
Suppose that we change our `true.dhall` example expression to depend on an older
348348
version of the Prelude (19.0.0):
@@ -415,7 +415,7 @@ like this:
415415
};
416416
```
417417
418-
## Overrides
418+
## Overrides {#ssec-dhall-overrides}
419419
420420
You can override any of the arguments to `buildDhallGitHubPackage` or
421421
`buildDhallDirectoryPackage` using the `overridePackage` attribute of a package.

0 commit comments

Comments
 (0)
Please sign in to comment.