Refusing to operate on extant directory

[Lupus]

It's not clear how to use this tool to update already existing vendor dir, wether it was created by cargo vendor or by cargo vendor-filterer - in both cases vendor-filterer bails out with this error: error: Refusing to operate on extant directory: vendor.

If I remove the vendor dir, it fails like this:

error: Executing cargo metadata (first run): Error during execution of `cargo metadata`: error: failed to get `anyhow` as a dependency of package `...` ...

Running cargo vendor without vendor dir works just fine and recreates it back. Same is true for an existing vendor dir - cargo vendor goes on and updates it.

I managed to recreate vendor dir with vendor-filterer by removing vendor dir and removing vendoring-related configuration out of .config/cargo.toml, but then I had to add this configuration back so that vendoring dir is in use by cargo. This sounds very cumbersone. Isn't there some better UX available? Updating vendor dir seems like a common pattern in a Rust project.

[deitch]

I just hit the same problem. If you try to run cargo build with vendoring configured into config.toml, it fails, as it should. But cargo vendor works without vendor/ (which makes sense).

Running cargo vendor-filterer, however, fails, as it depends on vendor already being in place.

How do we fix it?

[kugel-]

Stumbled on this as well. Makes me curious how to use the tool at all?

I thought that maybe I need full vendoring in a staging directory ( e.g. cargo vendor staging) but then 'vendor-filteredhas no way to specify that directory so a subsequentcargo vendor-filtered` still fails.

[kugel-]

FWIW, I think this is strictly related to #73 (or even a duplicate thereof).