doc: link, instead of just mentioning, Nix manual (#255126)
Instead of just telling the reader to go find the relevant section of the Nix manual, let's just link to it. Yay hypertext!
This commit is contained in:
parent
a29cf4aece
commit
b414f942e0
4 changed files with 6 additions and 5 deletions
|
@ -716,8 +716,8 @@ We've now seen how to create an ad-hoc temporary shell session, and how to
|
||||||
create a single script with Python dependencies, but in the course of normal
|
create a single script with Python dependencies, but in the course of normal
|
||||||
development we're usually working in an entire package repository.
|
development we're usually working in an entire package repository.
|
||||||
|
|
||||||
As explained in the Nix manual, `nix-shell` can also load an expression from a
|
As explained [in the `nix-shell` section](https://nixos.org/manual/nix/stable/command-ref/nix-shell) of the Nix manual, `nix-shell` can also load an expression from a `.nix` file.
|
||||||
`.nix` file. Say we want to have Python 3.11, `numpy` and `toolz`, like before,
|
Say we want to have Python 3.11, `numpy` and `toolz`, like before,
|
||||||
in an environment. We can add a `shell.nix` file describing our dependencies:
|
in an environment. We can add a `shell.nix` file describing our dependencies:
|
||||||
|
|
||||||
```nix
|
```nix
|
||||||
|
|
|
@ -32,7 +32,8 @@ Again, it's possible to launch the interpreter from the shell. The Ruby interpre
|
||||||
|
|
||||||
#### Load Ruby environment from `.nix` expression {#load-ruby-environment-from-.nix-expression}
|
#### Load Ruby environment from `.nix` expression {#load-ruby-environment-from-.nix-expression}
|
||||||
|
|
||||||
As explained in the Nix manual, `nix-shell` can also load an expression from a `.nix` file. Say we want to have Ruby 2.6, `nokogori`, and `pry`. Consider a `shell.nix` file with:
|
As explained [in the `nix-shell` section](https://nixos.org/manual/nix/stable/command-ref/nix-shell) of the Nix manual, `nix-shell` can also load an expression from a `.nix` file.
|
||||||
|
Say we want to have Ruby 2.6, `nokogori`, and `pry`. Consider a `shell.nix` file with:
|
||||||
|
|
||||||
```nix
|
```nix
|
||||||
with import <nixpkgs> {};
|
with import <nixpkgs> {};
|
||||||
|
|
|
@ -75,7 +75,7 @@ The name of the main binary for the package. This affects the binary `nix run` e
|
||||||
|
|
||||||
### `priority` {#var-meta-priority}
|
### `priority` {#var-meta-priority}
|
||||||
|
|
||||||
The *priority* of the package, used by `nix-env` to resolve file name conflicts between packages. See the Nix manual page for `nix-env` for details. Example: `"10"` (a low-priority package).
|
The *priority* of the package, used by `nix-env` to resolve file name conflicts between packages. See the [manual page for `nix-env`](https://nixos.org/manual/nix/stable/command-ref/nix-env) for details. Example: `"10"` (a low-priority package).
|
||||||
|
|
||||||
### `platforms` {#var-meta-platforms}
|
### `platforms` {#var-meta-platforms}
|
||||||
|
|
||||||
|
|
|
@ -24,7 +24,7 @@ The list of overlays is determined as follows.
|
||||||
|
|
||||||
2. Otherwise, if the Nix path entry `<nixpkgs-overlays>` exists, we look for overlays at that path, as described below.
|
2. Otherwise, if the Nix path entry `<nixpkgs-overlays>` exists, we look for overlays at that path, as described below.
|
||||||
|
|
||||||
See the section on `NIX_PATH` in the Nix manual for more details on how to set a value for `<nixpkgs-overlays>.`
|
See the [section on `NIX_PATH`](https://nixos.org/manual/nix/stable/command-ref/env-common.html#env-NIX_PATH) in the Nix manual for more details on how to set a value for `<nixpkgs-overlays>.`
|
||||||
|
|
||||||
3. If one of `~/.config/nixpkgs/overlays.nix` and `~/.config/nixpkgs/overlays/` exists, then we look for overlays at that path, as described below. It is an error if both exist.
|
3. If one of `~/.config/nixpkgs/overlays.nix` and `~/.config/nixpkgs/overlays/` exists, then we look for overlays at that path, as described below. It is an error if both exist.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue