nix 2 cli alternative to nix-store --query [drv] ?

[colemickens]

Describe the bug
How do I get the equivalent of this, with the new nix cli?

❯ nix-store --query /nix/store/svy43xnw42hpfygqk4r1wfzwsrx145kj-aarch64-linux-toplevel-bundle.drv
warning: unknown experimental feature 'ca-references'
/nix/store/z6cp88d6ww21n65vf5vviyfphq868nzy-aarch64-linux-toplevel-bundle

What I'm doing now is nix path-info --json [drv] but that queries all of the paths in the closure and is very non-trivial compared ot the nix-store --query:

drv="$(nix eval --raw "${thing}.drvPath" "${@}")"
out="$(nix path-info --json ${drv} | jq -r '.[0].path')" # very slow ...

❯ nix --version
nix (Nix) 2.6.0pre20211217_6e6e998

[balsoft]

What I ended up doing for this is to nix show-derivation | jq -r '.[].outputs.out.path'

But I do agree that replacements for nix-store --query are needed, especially --referrers and --tree.

[thufschmitt]

What I'm doing now is nix path-info --json [drv] but that queries all of the paths in the closure and is very non-trivial compared ot the nix-store --query:

Duh, it shouldn’t do a recursive query unless you pass --recursive:

$ nix path-info --json nixpkgs\#firefox
[{"path":"/nix/store/64nhgp9hyqkfi8i2ky5pk5csjcpl459f-firefox-94.0.2","valid":false}]

Also note that you can directly run it on an arbitrary installable, so your workaround could just be:

out="$(nix path-info --json ${thing} "${@} | jq -r '.[0].path')"

(That being said, I’ll put my “ca-derivations implementer” hat on and remark that this won’t work anymore with ca-derivations because the only way to know the output paths of a ca derivation is to build it).

[stale]

I marked this as stale due to inactivity. → More info