Skip to content

lambdageek/bad-vendor

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Repro steps:

  • Vendor:
cargo vendor --versioned-dirs --respect-source-config --no-delete > .cargo/config.toml
  • Vendor again:
cargo vendor --versioned-dirs --respect-source-config --no-delete

Expected

No changes on the filesystem outside of cargo's target dir. Either success or failure of the second cargo vendor operation. But no changes to any source code - including the files from the first invocation of cargo vendor.

Actual

The second cargo vendor fails with:

% cargo vendor --versioned-dirs --respect-source-config --no-delete
error: failed to sync

Caused by:
  failed to load pkg lockfile

Caused by:
  no matching package named `bytemuck` found
  location searched: directory source `/Users/alklig/work/bad_vendor/vendor` (which is replacing registry `crates-io`)
  required by package `bad_vendor v0.1.0 (/Users/alklig/work/bad_vendor)`

About

Example showing `cargo vendor ----respect-source-config` deletes previous vendored sources

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages