| Age | Commit message (Collapse) | Author |
|---|
|
Fixes #2894
|
|
Issue #2828.
|
|
|
|
unless specified
In `args@{ a ? 1 }: /* ... */` the value `a` won't be a part of `args`
unless it's specified when calling the function, the default value will
be ignored in this case.
My personal point of view is that this behavior is a matter of taste, at
least I was pretty sure that unmatched arguments will be a part of
`args@` while debugging some Nix code last week.
I decided to add a warning to the docs which hopefully reduces the
confusion of further Nix developers who thought the same about `args@`.
|
|
See commit 1bffd83e1a9
|
|
Imported from https://gist.github.com/edolstra/40da6e3a4d4ee8fd019395365e0772e7.
The goal is to turn this into an RFC eventually and later to integrate
it into the manual.
|
|
|
|
|
|
|
|
manual: "Nix Package collection" -> "Nixpkgs package collection".
|
|
For text files it is possible to do it like so:
`builtins.hashString "sha256" (builtins.readFile /tmp/a)`
but that doesn't work for binary files.
With builtins.hashFile any kind of file can be conveniently hashed.
|
|
Makes difference between Nix and Nixpkgs clearer to avoid
some common confusion this sentence on IRC.
Also disambiguate an "it" reference.
|
|
|
|
Bumped to 15.09 because older channels, when downloaded from
nixos.org, require firefox to be accessed via `pkgs.firefox`
|
|
this is added for completeness' sake since all the other possible
`builtins.typeOf` results have a corresponding `builtins.is<Type>`
|
|
This improves searchability.
|
|
fixes #2730.
|
|
It was just missing an `l` but should be fixed anyway.
|
|
|
|
Inside a derivation, exportReferencesGraph already provides a way to
dump the Nix database for a specific closure. On the command line,
--dump-db gave us the same information, but only for the entire Nix
database at once.
With this change, one can now pass a list of paths to --dump-db to get
the Nix database dumped for just those paths. (The user is responsible
for ensuring this is a closure, like for --export).
Among other things, this is useful for deploying a closure to a new
host without using --import/--export; one can use tar to transfer the
store paths, and --dump-db/--load-db to transfer the validity
information. This is useful if the new host doesn't actually have Nix
yet, and the closure that is being deployed itself contains Nix.
|
|
manual: "sandbox" option default is "true" on Linux
|
|
Fixes: 812e39313c ('Enable sandboxing by default')
|
|
- The instructions for using nix-shell as an interpreter has a Haskell script
example that doesn't work on more recent versions of Nix. Update the
instructions with a working command
|
|
|
|
The manual reference was commented out, and the sole reference to this
program other than the configure script. Removed both.
|
|
|
|
docs: add missing prerequisites: brotli, boost, libseccomp
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This was broken by some missing closing tags in 0bea4a50e03
|
|
Deprecate builtins.toPath
|
|
|
|
Closes #179.
|
|
|
|
preferLocalBuild does not in fact prevent substitution.
|
|
|
|
This prints the references graph of the store paths in the graphML
format [1]. The graphML format is supported by several graph tools
such as the Python Networkx library or the Apache Thinkerpop project.
[1] http://graphml.graphdrawing.org
|
|
`fetchurl` will now throw if given an `md5`, and the hashes have generally
been upgraded to avoid it and use `sha256` as a default. This updates the
documentation examples in the manual accordingly.
|
|
|
|
Update docs to describe how s3:// URLS does in fact support endpoint, region, and profile for upload
|
|
|
|
For example, this prevents a "kvm" build on machines that don't have
KVM.
Fixes #2012.
|
|
region, and profile for upload
|
|
Upgrade docs: improve the upgrade command
|
