mirror of
https://github.com/NixOS/nix
synced 2025-07-05 08:11:47 +02:00
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>
This commit is contained in:
parent
4a96125c3c
commit
e91596eb69
3 changed files with 47 additions and 12 deletions
|
@ -117,6 +117,12 @@ struct LockFlags
|
|||
/* Whether to commit changes to flake.lock. */
|
||||
bool commitLockFile = false;
|
||||
|
||||
/* The path to a lock file to read instead of the `flake.lock` file in the top-level flake */
|
||||
std::optional<std::string> referenceLockFilePath = std::nullopt;
|
||||
|
||||
/* The path to a lock file to write to instead of the `flake.lock` file in the top-level flake */
|
||||
std::optional<Path> outputLockFilePath = std::nullopt;
|
||||
|
||||
/* Flake inputs to be overridden. */
|
||||
std::map<InputPath, FlakeRef> inputOverrides;
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue