| Age | Commit message (Collapse) | Author |
|---|
|
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 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
|
|
|
|
|
|
as in [1], make the document structure visible, like in a template
[1]: 4655563470b59e0ef50a33af003058c2b54db778
|
|
|
|
|
|
it is not possible to antiquote numbers.
|
|
|
|
add removing users to uninstall instructions
|
|
|
|
manual: generalize anchor redirects
|
|
|
|
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).
|
|
Explain how Nix handles antiquotation of paths
|
|
|
|
Specifically, explain why Nix does not _re_evaluate paths during a
`nix repl` session. This is a thing that bit me while playing around
with paths and antiquotation in `nix repl` while reading the Nix
language tutorial at https://nix.dev/tutorials/nix-language.
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
|
|
|
|
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
amjoseph-nixpkgs/pr/doc/explain-local-remote-binary-substituter
|
|
refactor rendering command documentation to markdown
|
|
|
|
|
|
this allows readers to enter the code starting with what is visible from
the outside, instead of working themselves up from purely technical details.
|
|
|
|
it was quite a pain to manipulate strings just with `builtins`
|
|
idea:
- make document structure visible, like in a template
- order functions by descending abstraction
- avoid nested let bindings
|
|
|
|
|
|
add ccacheStdenv
|
|
when using ccache, rebuild time has been measured
89% faster while not slowing the speed of cold builds
|
|
Mainly:
- Try to triangulate between narrative that framed this as
a new/easy process and the need for a reference that will
not quickly grow stale.
- Fix a ~continuity issue where the text was talking about
"your Cachix cache" before saying that you'd need to make
a Cachix cache to enable the installer tests.
- Adopt suggestion on titling, and nest subtitles in the
installer test section.
|
|
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
|
|
|
|
|
|
|
|
|
