Alexander Bantyev 2664a216e5 flake.cc: computeLocks: Only verify overrides when they could change ... When we check for disappeared overrides, we can get "false positives" for follows and overrides which are defined in the dependencies of the flake we are locking, since they are not parsed by parseFlakeInputs. However, at that point we already know that the overrides couldn't have possible been changed if the input itself hasn't changed (since we check that oldLock->originalRef == *input.ref for the input's parent). So, to prevent this, only perform this check when it was possible that the flake changed (e.g. the flake we're locking, or a new input, or the input has changed and mustRefetch == true).		2021-12-28 15:30:06 +03:00
..
call-flake.nix	Represent 'follows' inputs explicitly in the lock file	2020-06-11 14:40:21 +02:00
config.cc	flakes: fix boolean and int nixConfig values	2021-11-29 15:53:22 +01:00
flake.cc	flake.cc: computeLocks: Only verify overrides when they could change	2021-12-28 15:30:06 +03:00
flake.hh	If we can't write a lock file, pretend the top-level flake is dirty	2021-09-15 18:31:42 +02:00
flakeref.cc	Re-allow inputs.x.url = "/path/to/file"	2021-12-13 20:59:33 +01:00
flakeref.hh	Re-allow inputs.x.url = "/path/to/file"	2021-12-13 20:59:33 +01:00
lockfile.cc	In flake lock file diffs, show the last-modified date of inputs if available	2021-08-11 19:35:28 +02:00
lockfile.hh	Capitalize JSON for consistency	2020-10-28 17:54:28 -05:00