Skip to content

Comments

docs: remove incorrect claim re gc --print-dead#14394

Merged
edolstra merged 1 commit intoNixOS:masterfrom
me-and:no-print-dead-space-usage
Oct 28, 2025
Merged

docs: remove incorrect claim re gc --print-dead#14394
edolstra merged 1 commit intoNixOS:masterfrom
me-and:no-print-dead-space-usage

Conversation

@me-and
Copy link
Member

@me-and me-and commented Oct 28, 2025

Motivation

Update the nix-store --gc documentation to match its actual behaviour.

Ideally the behaviour of nix-store --gc would be updated to re-add function that was removed, and that has been requested in #7591, but that is a much more significant change. In the meantime, it's useful to at least have the documentation match the expected behaviour.

Context

In 4250b64, nix-store --gc --print-dead gained the ability to report how much space would be freed by running garbage collection. Based on code reading and git bisect, I think that function broke in 7ab6896, but the documentation wasn't updated at that time.


Add 👍 to pull requests you find important.

The Nix maintainer team uses a GitHub project board to schedule and track reviews.

Summary by CodeRabbit

  • Documentation
    • Updated nix-store --gc command documentation to clarify default output behavior regarding bytes freed with the --print-dead flag.

Per NixOS#7591, the `nix-store --gc --print-dead` command does not provide
any feedback about the amount of disk space that is used by dead store
paths.  It looks like this has been the case since 7ab6896 (* Garbage
collector: added an option `--use-atime' to delete paths in...,
2008-09-17).

Update the nix-store documentation to remove the claim that this is
function that `nix-store --gc --print-dead` performs.
@coderabbitai

This comment has been minimized.

@edolstra edolstra added this pull request to the merge queue Oct 28, 2025
Merged via the queue into NixOS:master with commit 1a4ad07 Oct 28, 2025
18 checks passed
@edolstra edolstra mentioned this pull request Dec 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants