diff options
| author | tv <tv@krebsco.de> | 2026-11-14 01:24:34 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-14 02:45:43 +0100 |
| commit | 361b504079389cfd6f8cf3160da96b88cc5e5a69 (patch) | |
| tree | a74d65e8365b9244211057aaeac144de83bae546 /pkgs/populate/lib/types/posix.nix | |
| parent | e4991d754160dd851b980f142e4b9a23815eafa3 (diff) | |
Whether a derived copy of a flake or flake-input source needs to be
made again depends on the sources it draws inputs from. For one that
isn't in the store, the key had its hash, so every run read all of it,
e.g. all of a nixpkgs work tree, .git included, which takes long even
when nothing changed. For a Git work tree that Nix gets as git+file:,
whose commit and tracked files are all Nix uses, the key has its
commit instead, if no tracked file differs from it, which Git tells
quickly. git_flake decides what Nix gets as git+file:, for resolve as
well.
Keys of copies drawing from such work trees change once, so those
copies get made again on the first run, also after deploying with
krops 1.
rewrite-cache-git checks that such a copy gets made again for a new
commit, but not for redeploying, nor for an untracked file.
Diffstat (limited to 'pkgs/populate/lib/types/posix.nix')
0 files changed, 0 insertions, 0 deletions
