Linus Heckemann e91596eb69 Allow specifying alternative paths for reading/writing flake locks ... This allows having multiple separate lockfiles for a single project, which can be useful for testing against different versions of nixpkgs; it also allows tracking custom input overrides for remote flakes without requiring local clones of these flakes. For example, if I want to build Nix against my locally pinned nixpkgs, and have a lock file tracking this override independently of future updates to said nixpkgs: nix flake lock --output-lock-file /tmp/nix-flake.lock --override-input nixpkgs flake:nixpkgs nix build --reference-lock-file /tmp/nix-flake.lock Co-Authored-By: Will Fancher <elvishjerricco@gmail.com>		2023-03-13 21:08:52 +01:00
..
call-flake.nix	flakes: Differentiate self.outPath and self.sourceInfo.outPath	2023-02-22 03:31:24 +01:00
config.cc	printMsg replacement by printInfo	2022-12-16 09:34:22 +01:00
flake.cc	Allow specifying alternative paths for reading/writing flake locks	2023-03-13 21:08:52 +01:00
flake.hh	Allow specifying alternative paths for reading/writing flake locks	2023-03-13 21:08:52 +01:00
flakeref.cc	Split OutputsSpec and ExtendedOutputsSpec, use the former more	2023-01-11 18:57:18 -05:00
flakeref.hh	Rename OutputPath -> ExtendedOutputPath	2023-01-11 18:55:29 -05:00
lockfile.cc	Fix clang compilation	2023-02-01 20:34:44 +01:00
lockfile.hh	Trivial changes from the lazy-trees branch	2022-12-07 14:06:34 +01:00