| Age | Commit message (Collapse) | Author |
|---|
|
Flake lock file updates:
• Updated input 'nixpkgs':
'github:NixOS/nixpkgs/82891b5e2c2359d7e58d08849e4c89511ab94234' (2021-09-28)
→ 'github:NixOS/nixpkgs/530a53dcbc9437363471167a5e4762c5fcfa34a1' (2022-02-19)
|
|
|
|
Allow `welcomeText` when checking a flake template
|
|
Fix https://github.com/NixOS/nix/issues/6321
|
|
|
|
fix(run): set applyNixConfig lockFlag
|
|
|
|
profile!: consistent use of url/uri. create new version
|
|
Fix handling of outputHash when outputHashAlgo is not specified
|
|
https://hydra.nixos.org/build/171351131
|
|
scripts/install-systemd-multi-user.sh: fix another typo
|
|
|
|
Impure derivations
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Impure derivations are derivations that can produce a different result
every time they're built. Example:
stdenv.mkDerivation {
name = "impure";
__impure = true; # marks this derivation as impure
outputHashAlgo = "sha256";
outputHashMode = "recursive";
buildCommand = "date > $out";
};
Some important characteristics:
* This requires the 'impure-derivations' experimental feature.
* Impure derivations are not "cached". Thus, running "nix-build" on
the example above multiple times will cause a rebuild every time.
* They are implemented similar to CA derivations, i.e. the output is
moved to a content-addressed path in the store. The difference is
that we don't register a realisation in the Nix database.
* Pure derivations are not allowed to depend on impure derivations. In
the future fixed-output derivations will be allowed to depend on
impure derivations, thus forming an "impurity barrier" in the
dependency graph.
* When sandboxing is enabled, impure derivations can access the
network in the same way as fixed-output derivations. In relaxed
sandboxing mode, they can access the local filesystem.
|
|
libexpr: Throw the correct error in toJSON
|
|
|
|
bundler: update default bundler to support new bundler API
|
|
|
|
|
|
The return value of BaseError::addTrace(...) is never used and
error-prone as subclasses calling it will return a BaseError instead of
the subclass.
This commit changes its return value to be void.
|
|
BaseError::addTrace(...) returns a BaseError, but we want to
throw a TypeError instead.
Fixes #6336.
|
|
Gitignore or don’t create some build outputs
|
|
|
|
|
|
nix-daemon.service: require mounts for /nix/var/nix/db
|
|
Users may want to mount a filesystem just for the Nix database, with
the filesystem's parameters specially tuned for sqlite. For example, on
ZFS you might set the recordsize to 64k after changing the database's
page size to 65536.
|
|
Simplify the handling of the hash modulo
|
|
Rather than having four different but very similar types of hashes, make
only one, with a tag indicating whether it corresponds to a regular of
deferred derivation.
This implies a slight logical change: The original Nix+multiple-outputs
model assumed only one hash-modulo per derivation. Adding
multiple-outputs CA derivations changed this as these have one
hash-modulo per output. This change is now treating each derivation as
having one hash modulo per output.
This obviously means that we internally loose the guaranty that
all the outputs of input-addressed derivations have the same hash
modulo. But it turns out that it doesn’t matter because there’s nothing
in the code taking advantage of that fact (and it probably shouldn’t
anyways).
The upside is that it is now much easier to work with these hashes, and
we can get rid of a lot of useless `std::visit{ overloaded`.
Co-authored-by: John Ericson <John.Ericson@Obsidian.Systems>
|
|
nix {run,shell}: Print a better error message if the store is not local
|
|
nix profile install: Don't use queryDerivationOutputMap()
|
|
Closes #6317
|
|
Instead get the outputs from Installable::build(). This will also
allow 'nix profile install' to support impure derivations.
Fixes #6286.
|
|
scripts/install-systemd-multi-user.sh: fix typo
|
|
sytemd-tmpfiles -> systemd-tmpfiles
|
|
Only provide builtins is the corresponding experimental feature is enabled
|
|
Make buildPathsWithResults() only return info on wanted outputs
|
|
|
|
Fixes #5523.
|
|
experimental feature is enabled
This allows writing fallback code like
if builtins ? fetchClosure then
builtins.fetchClose { ... }
else
builtins.storePath ...
|
