| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
Fixes #7026.
|
|
Trivial changes from the lazy-trees branch
|
|
|
|
|
|
|
|
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
Update uninstall guide involving systemd
|
|
refactor rendering documentation of options
|
|
this is a follow-up on e7dcacb.
most links are relative and this should not be too much of a detriment.
|
|
this avoids incorrect rendering on the man pages, since `lowdown`
neither parses the anchor syntax nor HTML.
this should rather be fixed in lowdown, as adding more anchors
would otherwise produce ever more noise and error-prone repetition.
|
|
|
|
|
|
* docs: Use secret-key-files when demonstrating post-build-hooks
The docs used to recommend calling `nix store sign` in a post-build
hook, but on more recent versions of nix, this results in unsigned
store paths being copied into binary caches. See
https://github.com/NixOS/nix/issues/6960 for details.
Instead, use the `secret-key-files` config option, which signs all
locally-built derivations with the private key.
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
These only functioned if a very narrow combination of conditions held:
- The result path does not yet exist (--check did not result in
repeated builds), AND
- The result path is not available from any configured substituters, AND
- No remote builders that can build the path are available.
If any of these do not hold, a derivation would be built 0 or 1 times
regardless of the repeat option. Thus, remove it to avoid confusion.
|
|
|
|
this is a quick half-fix for command line examples, as discussed
discussed in [1].
[1]: https://github.com/NixOS/nix/pull/7389
examples which look like this
$ foo bar
baz
are confusing for Unix shell beginners, because it's hard to discern
what is supposed to be entered into the actual command line when the
convention of prefixing `$` is not known, as barely any real-world shell
looks that way any more.
this change prevents selecting the prompt part with the mouse in the
HTML representation of the Nix manual.
it does not prevent selecting the output part of the shell example.
it also does not address that the copy button provided by mdBook takes
the entire sample, including the prompts, into the clipboard.
|
|
docs: drop shell prompt character for consistency
|
|
this makes more obvious what the code produces, and the structure of the
output easier to change
|
|
this is where it belongs and can be found together with the other
options.
|
|
|
|
refactor rendering documentation of builtins
|
|
|
|
|
|
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
|
|
as in [1], make the document structure visible, like in a template
[1]: 4655563470b59e0ef50a33af003058c2b54db778
|
|
|
|
|
|
it is not possible to antiquote numbers.
|
|
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
|
|
Co-authored-by: sequencer <liu@jiuyang.me>
|
|
|
|
add removing users to uninstall instructions
|
|
|
|
manual: generalize anchor redirects
|
|
the language has its own overview page where its properties are
described in sufficient detail.
|
|
this will at some point enable rendering them nicely for the web
|
|
Co-authored-by: Bryan Honof <bryan.honof@tweag.io>
|
|
|
|
these changes were not merged properly and had to be reverted.
see merge commit d8e54d19f71f78540dd967b2e42be6a5d8a0b1bb for full
history leading up to here.
|
|
|
|
add syntax overview from NixOS manual
|
|
|
|
after discussing this with multiple people, I'm convinced that "build
task" is more precise: a derivation is not an action, but inert until it
is built. also it's easier to pronounce.
proposal: use "build task" for the generic concept "description of how
to derive new files from the contents of existing files". then it will
be easier to distinguish what we mean by "derivation" (a specific data
structure and Nix language value type) and "store derivation" (a
serialisation of a derivation into a file in the Nix store).
|
