No objection to the addition but why aren't you just passing `--bins` to cargo? That would get you all the binaries without having to specify any names. Another related topic might be creating example executables (as dedicated output?). Sometimes libraries provide example implementations that are all one really needs.

Wow. I wasn't aware that `cargo` would handle it like that. Looking at the `Cargo.toml` of the project it seems like it should be able to build both binaries (with different names): ```toml [[bin]] name = "sccache" [[bin]] name = "sccache-dist" required-features = ["dist-server"] ``` In that case that flag actually makes sense but probably is also worth an upstream (as in cargo) bug. It should just create the `sccache-dist` bin with the proper name as defined in the `Cargo.toml`. LGTM 👍

This sounds more like you need a multiple output derivation. You would move binaries in a dedicated output that users then can select. This has the benefit of doing the whole dependency compilation only once and not for every other binary that package might provide. If you then need another version of `sccache-dist` you would override the source (as usual) and just pick the `.dist` output. That would be something you do during `installPhase`. You move some binaries to another output. ``` … buildRustPackage { … outputs = [ "out" "dist" ]; postInstall = '' moveToOutput "bin/sccache-dist" "$dist" ''; } ``` In `pkgs/top-level/all-packages.nix` you would then just refer to them like this: ``` sccache = pkgs.callPackage ./somewhere.nix {}; sccache-dist = sccache.dist; ``` In your system configuration you would then just say ``` environment.systemPackages = [ pkgs.sccache.dist ]; ``` to only install the `dist` output.