On Mon, 21 Sep 2026 17:21:32 +1000 Reuben Roessler <[email protected]> wrote: > Package: cargo > Version: 1.93.1ubuntu1 > Severity: normal > Tags: patch > X-Debbugs-Cc: [email protected] > > Dear Maintainer, > > The wrapper for cargo install forces the --path option for "cargo > install" to the current working directory. This fails for projects > which use a virtual manifest file (eg: declares a [workspace] instead > of a [package]). > > I am submitting a patch that will allow developers to override the > installation path option so that they can install a selected crate.
It seems Ubuntu is carrying more delta for the cargo wrapper which makes this patch unappliable. Could you either send a cleaned up version matching Debian's copy of the script, or upstream the other changes first if they would benefit us on the Debian side? I am not sure whether overriding the install path has any benefits over just calling `cargo build -p <foo>`, but it should be possible to support it. We could also make the injection of `--path ..` by the wrapper conditional on no path being passed already, which would support calling the wrapper with a path override? We already have similar logic for dropping `--quiet` if the arguments include `--verbose`. I am happy to take MRs on salsa as well, if you prefer that. Fabian
