4 ms·
I 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 up
by tonyfinn 4y ago
I 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.