You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem you are trying to solve
We would like to vendor all of our dependencies and transitive dependencies, such that cargo does not make network requests when running in our project.
We can currently do this by issuing the --frozen argument to cargo, but that is a manual process. It would be better if we could make this the default in our repository-wide .cargo/config file.
Describe the solution you'd like
We'd like an option added to .cargo/config to make --frozen the default cargo behavior. The new option may belong under [net].
Notes
We are currently using the following workaround:
[http]
proxy = "socks://proxy.invalid/"
This produces less-than-ideal error messages, and is of course not a very clean solution.
The text was updated successfully, but these errors were encountered:
Actually, it turns out --frozen isn't quite what I needed: I needed a way to prevent network requests. --frozen additionally requires Cargo.lock to be up to date.
This feature request is for a way to prevent network requests (as the proxy hack does), not a .cargo/config clone of --frozen.
I believe that's exactly the functionality I'm looking for! I'm requesting that it be added as an option in .cargo/config, so that we can confirm that cargo runs without network requests.
If you think this request belongs in #5655 instead, let me know and I'll comment there and mark this as a duplicate.
Describe the problem you are trying to solve
We would like to vendor all of our dependencies and transitive dependencies, such that cargo does not make network requests when running in our project.
We can currently do this by issuing the
--frozen
argument to cargo, but that is a manual process. It would be better if we could make this the default in our repository-wide .cargo/config file.Describe the solution you'd like
We'd like an option added to .cargo/config to make
--frozen
the default cargo behavior. The new option may belong under[net]
.Notes
We are currently using the following workaround:
This produces less-than-ideal error messages, and is of course not a very clean solution.
The text was updated successfully, but these errors were encountered: