3 ms·
And vice versa. It's tricky to know what the binary will actually be named. I have had to look directly in the /nix/store enough times that I lost count.
by thomastjeffery 4y ago
And vice versa. It's tricky to know what the binary will actually be named.
I have had to look directly in the /nix/store enough times that I lost count.
- tonyfinn 4y agoI will say this is not a nix specific problem and also not trivially solvable by policy because of packages that contain multiple binaries as produced by the upstream developer (e.g. grep/fgrep/egrep, pacman/makepkg/pacman-key, , go/gofmt, ffmpeg/ffprobe, qemu has about a billion, etc.).
- thomastjeffery 4y agoIt would be trivial to print the contents of the nix store that package uses. It would be pretty straightforward to show only what ends up in the path.