puck/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity

Merge pull request #7455 from rapenne-s/documentation_fix

Browse source 
Add anchors and links to definition
This commit is contained in:
Eelco Dolstra 2022-12-13 17:26:52 +01:00 committed by GitHub
parent e2a4e7aecd 09860c16ce
commit 46b3c026fc
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 41 additions and 36 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/libcmd/common-eval-args.cc
View file

@ -77,7 +77,7 @@ MixEvalArgs::MixEvalArgs()
branch in the `nixpkgs` repository.
The URLs of the tarballs from the official `nixos.org` channels
(see [the manual page for `nix-channel`](nix-channel.md)) can be
(see [the manual page for `nix-channel`](../nix-channel.md)) can be
abbreviated as `channel:<channel-name>`. For instance, the
following two flags are equivalent:
@ -86,7 +86,7 @@ MixEvalArgs::MixEvalArgs()
-I nixpkgs=https://nixos.org/channels/nixos-21.05/nixexprs.tar.xz
```
You can also fetch source trees using flake URLs and add them to the
You can also fetch source trees using [flake URLs](./nix3-flake.md#url-like-syntax) and add them to the
search path. For instance,
```

11
src/nix/flake.md
View file

@ -18,7 +18,10 @@ values such as packages or NixOS modules provided by the flake).
Flake references (*flakerefs*) are a way to specify the location of a
flake. These have two different forms:
* An attribute set representation, e.g.
## Attribute set representation
Example:
```nix
{
@ -31,7 +34,9 @@ flake. These have two different forms:
The only required attribute is `type`. The supported types are
listed below.
* A URL-like syntax, e.g.
## URL-like syntax
Example:
```
github:NixOS/nixpkgs
@ -62,7 +67,7 @@ flake. These have two different forms:
};
```
## Examples
### Examples
Here are some examples of flake references in their URL-like representation: