nix3-store-diff-closures(1)

πŸ“¦
version 2.35.3 Β· 13 versions
, in fedora 44

πŸ’– nix3-store-diff-closures(1) πŸ’–

ok so bestie, you know how sometimes you update your system and everything shifts around and you're like "what even changed"? this is the page for that. it lives in the General Commands Manual, and it's about to become your new fave. ✨

⚠️ Warning β€” this program is experimental and its interface is subject to change. (translation: don't build your entire personality around the exact flags, okay? πŸ™ˆ)

🌸 NAME 🌸

nix store diff-closures β€” show what packages and versions were added and removed between two closures

πŸ¦‹ SYNOPSIS πŸ¦‹

nix store diff-closures [option…] before after

✨ EXAMPLES ✨

  • Show what got added and removed between two versions of the NixOS system profile:
# nix store diff-closures /nix/var/nix/profiles/system-655-link /nix/var/nix/profiles/system-658-link
acpi-call: 2020-04-07-5.8.16 β†’ 2020-04-07-5.8.18
baloo-widgets: 20.08.1 β†’ 20.08.2
bluez-qt: +12.6 KiB
dolphin: 20.08.1 β†’ 20.08.2, +13.9 KiB
kdeconnect: 20.08.2 β†’ βˆ…, -6597.8 KiB
kdeconnect-kde: βˆ… β†’ 20.08.2, +6599.7 KiB
…

like… look at it. it's giving receipts. πŸ’…

πŸ’œ DESCRIPTION πŸ’œ

This command shows the differences between the two closures before and after, specifically around the addition, removal, or version change of packages, plus changes in store path sizes.

For each package name in the two closures β€” and bestie, a "package name" here is defined as the name component of a store path excluding the version β€” if there's a change in the set of versions of the package, or a change in the size of the store paths of more than 8 KiB, it prints a line like this:

dolphin: 20.08.1 β†’ 20.08.2, +13.9 KiB

No size change is shown if it's below that threshold. (sub-threshold changes are lowkey invisible, sorry 🫢)

If the package doesn't exist in either the before or after closure, it's represented using βˆ… (the empty set) on the appropriate side of the arrow. If a package has an empty version string, the version is rendered as Ξ΅ (epsilon).

Also!! There may be multiple versions of a package in each closure. In that case, only the changed versions are shown. So like:

libfoo: 1.2, 1.3 β†’ 1.4

…this leaves open the possibility that there are other versions (e.g. 1.1) that exist in both closures. it's not hiding them from you, it's just not mentioning them. periodt.

🌈 OPTIONS 🌈

πŸŽ€ Common evaluation options

  • --arg name expr β€” pass the value expr as the argument name to Nix functions.
  • --arg-from-file name path β€” pass the contents of file path as the argument name to Nix functions.
  • --arg-from-stdin name β€” pass the contents of stdin as the argument name to Nix functions.
  • --argstr name string β€” pass the string string as the argument name to Nix functions.
  • --debugger β€” start an interactive environment if evaluation fails. (your little debugging safe space πŸ’–)
  • --eval-store store-url β€” the URL of the Nix store to use for evaluation, i.e. to store derivations (.drv files) and inputs referenced by them.
  • --impure β€” allow access to mutable paths and repositories. (living dangerously, iconic)
  • --include / -I path β€” add path to search path entries used to resolve lookup paths.
    • This option may be given multiple times.
    • Paths added through -I take precedence over the nix-path configuration setting and the NIX_PATH environment variable.
  • --override-flake original-ref resolved-ref β€” override the flake registries, redirecting original-ref to resolved-ref.
  • --commit-lock-file β€” commit changes to the flake's lock file.
  • --inputs-from flake-url β€” use the inputs of the specified flake as registry entries.
  • --no-registries β€” don't allow lookups in the flake registries.
🚫 DEPRECATED β€” use --no-use-registries instead.
  • --no-update-lock-file β€” do not allow any updates to the flake's lock file.
  • --no-write-lock-file β€” do not write the flake's newly generated lock file.
  • --output-lock-file flake-lock-path β€” write the given lock file instead of flake.lock within the top-level flake.
  • --override-input input-path flake-url β€” override a specific flake input (e.g. dwarffs/nixpkgs). The input path must not be empty. This implies --no-write-lock-file.
  • --recreate-lock-file β€” recreate the flake's lock file from scratch.
🚫 DEPRECATED β€” use nix flake update instead.
  • --reference-lock-file flake-lock-path β€” read the given lock file instead of flake.lock within the top-level flake.
  • --update-input input-path β€” update a specific flake input (ignoring its previous entry in the lock file).
🚫 DEPRECATED β€” use nix flake update instead.
  • --debug β€” set the logging verbosity level to 'debug'.
  • --log-format format β€” set the format of log output; one of raw, internal-json, bar or bar-with-logs.
  • --print-build-logs / -L β€” print full build logs on standard error.
  • --quiet β€” decrease the logging verbosity level.
  • --verbose / -v β€” increase the logging verbosity level.

⭐ Miscellaneous global options

  • --help β€” show usage information.
  • --offline β€” disable substituters and consider all previously downloaded files up-to-date.
  • --option name value β€” set the Nix configuration setting name to value (overriding nix.conf).
  • --refresh β€” consider all previously downloaded files out-of-date.
  • --repair β€” during evaluation, rewrite missing or corrupted files in the Nix store. During building, rebuild missing or corrupted store paths.
  • --version β€” show version information.

πŸ”₯ Options that change the interpretation of installables

  • --derivation β€” operate on the store derivation rather than its outputs.
  • --expr expr β€” interpret installables as attribute paths relative to the Nix expression expr.
  • --file / -f file β€” interpret installables as attribute paths relative to the Nix expression stored in file. If file is the character -, then a Nix expression is read from standard input. Implies --impure.
πŸ“ Note β€” see man nix.conf for overriding configuration settings with command line flags.

and that's the whole page, bestie!! πŸ₯° one last thing: this whole vibe check comes from the General Commands Manual, page nix3-store-diff-closures(1) β€” so if you ever need to find it again, that's the name to search. go forth and diff those closures, you absolute main character. πŸ‘‘πŸ’–

πŸ“¦ where this page comes from