Seeing dependents of a package, as the leaf-level human-readable package names

whoa neat UI in nix-tree. So that helped me get my ultimate answer: what depends on “freeimage”? answer: nixos, maybe?

I see nix-tree handles both answers to (a) and (b) entirely in its GUI:

  • a) search (/) followed by yank gets you a path.
  • b) pass a path in as the first arg of nix-tree and you get the package.

But I just tried both with gimp and I’m pretty sure that’s only installed because I installed it, and I’m not sure if that’s what the why-depends feature is trying to show me or not. This got me to search the forums again and I found this interesting: “there is no solution” discussion


separately: I’d still be interested if there was a single command (not a gui) that could give these answers!

I found a previous post about this that dumps all data, so I guess I could scrape that (the later commands in that thread don’t work for me even with all the --extra-experimental-features flags passed in). I’m just surprised there’s not a single command that will do this… I’ll keep hunting.