-
Notifications
You must be signed in to change notification settings - Fork 30
Support for path dependencies #25
Comments
Note that Cargo itself doesn't have support for this, so this would likely need to be implemented there first. |
cargo-vendor is nice with Docker to not have to re-download everything but we still need to recompile everything. If caching is the solution to that maybe I don't need support for path dependencies. |
Oh so typically path dependencies are idiomatically within the same "repository" or working-directory ish, when using path dependencies across the filesystem and/or other repos you'll typically want to use something like |
What about support |
Cargo supports path-relative dependencies, but cargo vendor doesn't @alexcrichton . This means I can't use a Dockerfile to create a docker image of a project I'm working on if that project isn't published in git or crates.io. There are hacky workarounds, but it would be great if vendor worked on paths. |
This crate is now included natively in Cargo as of rust-lang/cargo#6869 and today's nightly Rust. I'm closing all issues in this repository before I archive the repository, but if you're still interested in seeing this issue fixed then please feel free to file an issue with Cargo itself! |
I have some dependencies like this:
cargo-vendor doesn't seem to include them in the vendor directory. Normally it's not needed except when using Docker.
The text was updated successfully, but these errors were encountered: