| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This line has been this way since it was written, in 9e08f5efe
in 2006.
I think it was just a small mistake then; Eelco's thesis earlier
that year says the permission on each file is set to 0444 or 0555
in a derivation's output as part of the build process. In any
case I'm pretty sure that's the behavior now.
|
|
Running `nix-store --gc --delete` will, as of Nix 2.3.3, simply fail
because the --delete option conflicts with the --delete operation.
$ nix-store --gc --delete
error: only one operation may be specified
Try 'nix-store --help' for more information.
Furthermore, it has been broken since at least Nix 0.16 (which was
released sometime in 2010), which means that any scripts which depend
on it should have been broken at least nine years ago. This commit
simply formally removes the option. There should be no actual difference
in behaviour as far as the user is concerned: it errors with the exact
same error message. The manual has been edited to remove any references
to the (now gone) --delete option.
Other information:
* Path for Nix 0.16 used:
/nix/store/rp3sgmskn0p0pj1ia2qwd5al6f6pinz4-nix-0.16
|
|
display attr-path only when queried available
|
|
|
|
Fixes #3396.
|
|
This file is licensed under the GPL. Originally, Nix was also
GPL-licensed so that was fine. However, we later changed the license
to the LGPL but missed the fact that style.css has an incompatible
license.
Since the Nix manual at nixos.org uses its own styling, we can remove
this file.
Fixes #3392.
|
|
|
|
Document that autoconf is a dependency
|
|
|
|
The flag is `--pure-eval`, which can be found by looking at the test suite; it
should be in the notes describing the feature as well, since otherwise users may
assume this is referencing something like `nix-shell --pure`.
|
|
|
|
- At the top of the release notes, we announce sandboxing is now enabled by default,
then at the bottom it says it's now disabled when missing kernel support. These
can be merged into one point for clarity.
- The point about `max-jobs` defaulting to 1 appears unrelated to sandboxing.
|
|
|
|
|
|
This makes it possible to reference single attribute definitions,
for pointing people to their exact definition.
|
|
|
|
|
|
|
|
|
|
This documents the outcome of the change in
https://github.com/NixOS/nix/issues/454:
> We can also automatically add parentheses in the generated
> `buildInputs`, so you can type `nix-shell -p "expr"`
> instead of `"(expr").
|
|
|
|
|
|
Update man to show that nix-shell allows --arg
|
|
docs: fix upper bound on number of consumed cores
|
|
docs: xref doesn't render in title
|
|
|
|
The `post-build-hook` text currently appears in the index, but not on the actual title line of the section, this follows the pattern used in a previous section to get a reference into a title.
|
|
|
|
|
|
Remove superfluous IAM action for S3 cache
|
|
`s3:ListObjects` isn't a real IAM action, but _is_ the name of an S3 API method. `s3:ListBucket` is the relevant action for that method.
https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazons3.html
|
|
|
|
|
|
This reverts commit d8730fb86facadbef22d3df7f8a743a56e7ed53c.
|
|
|
|
nix-channel documentation: don't suggest deprecated function
|
|
|
|
docs: Note that tryEval doesn't do deep evaluation
|
|
1. remove a typo space
2. Simplify negative style by using affirmative style
|
|
|
|
With the merge of #2582, the syntax "tags/1.9" for refs does not work
anymore.
However, the new syntax "refs/tags/1.9" seems to support annotated tags,
such as "refs/tags/2.0".
Closes #2385.
|
|
|
|
|
|
|
|
|
|
Fix nix-env documentation for --delete-generations
|
|
My attempt at clarifying the docs resulted in a false explanation. This
is now fixed and I added an example to eliminate all possible confusion.
|
|
|
|
|
