Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cargo config #3788

Closed
SRGOM opened this issue Mar 2, 2017 · 4 comments
Closed

Cargo config #3788

SRGOM opened this issue Mar 2, 2017 · 4 comments

Comments

@SRGOM
Copy link

SRGOM commented Mar 2, 2017

No description provided.

@alexcrichton
Copy link
Member

Could you elaborate on the rationale for such a feature as well? In general we try to avoid configuration where building a project involves cloning followed by configuration of Cargo itself, but I'm curious to hear how you ran into this!

@alexcrichton
Copy link
Member

Thanks for the explanation! I wonder, would this scheme for prepublish fit your use case? (I think it sounds like it does)

@alexcrichton
Copy link
Member

@SRGOM oh well it doesn't have even an RFC yet so it's up in the air, but the idea is that it supports the concept of "assume these crates are from the registry, even though they're not. That way you'd say in your local configuration "append these crates to the crates.io registry" and then you'd write you Cargo.toml as-if you had published those crates, even if you hadn't.

@alexcrichton
Copy link
Member

Ok well in that case I think I'm going to close in favor of #2649 (comment) which is itself still in flux so we have yet to see how the dust settles on that issues anyway. Thanks for the report though!

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

No branches or pull requests

2 participants