Skip to content
This repository has been archived by the owner on Jun 21, 2019. It is now read-only.

Support for path dependencies #25

Closed
bbigras opened this issue Mar 26, 2017 · 6 comments
Closed

Support for path dependencies #25

bbigras opened this issue Mar 26, 2017 · 6 comments

Comments

@bbigras
Copy link

bbigras commented Mar 26, 2017

I have some dependencies like this:

mydep = { path = "/some/path" }

cargo-vendor doesn't seem to include them in the vendor directory. Normally it's not needed except when using Docker.

@alexcrichton
Copy link
Owner

Note that Cargo itself doesn't have support for this, so this would likely need to be implemented there first.

@bbigras
Copy link
Author

bbigras commented Mar 28, 2017

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.

@alexcrichton
Copy link
Owner

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 [replace] or git dependencies instead.

@XX
Copy link

XX commented Feb 26, 2018

What about support path now?

@autodidaddict
Copy link

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.

@alexcrichton
Copy link
Owner

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!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants