Alexander Bantyev 169ea0b83f Flake follows: resolve all follows to absolute ... It's not possible in general to know in computeLocks, relative to which path the follows was intended to be. So, we always resolve follows to their absolute states when we encounter them (which can either be in parseFlakeInput or computeLocks' fake input population). Fixes https://github.com/NixOS/nix/issues/6013 Fixes https://github.com/NixOS/nix/issues/5609 Fixes https://github.com/NixOS/nix/issues/5697 (again)		2022-02-02 21:41:45 +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 follows: resolve all follows to absolute	2022-02-02 21:41:45 +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	Add more tests for flake upward searching	2022-01-14 17:21:18 +03: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