Open ericonr opened 3 years ago
Comparing with Nix and Arch shows that cargo install
is not suitable for our purpose (and cannot be made), so I'd suggest we manually grab the binaries from the build dir as these distros do.
This might have something to do with this issue I reported on Rust forums (now reported on Cargo's repo too). Overriding do_install
to just grab the binary generated during do_build
makes total sense to me. :slightly_smiling_face:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
I've hit this in https://github.com/void-linux/void-packages/pull/37013, and I know what might be happening in the case of all of those packages. Essentially cargo arbitrarily decides to drop a feature from a transient dependency (with no indication of why). You can see it when comparing the command cargo runs at build and at install for the deepest dependency that gets rebuilt (the command is shown when adding -vv
).
In the case of #37013, the dependency that gets rebuilt is syn
because cargo drops its full
feature. There's no apparent reason for that drop, and it might even be a bug somewhere. The short-term fix was to explicitly add that feature for that dependency in the top crate's Cargo.toml.
At least
rust-analyzer
andangle-grinder
. Example below