Crates come from crates.io. There is no support for a private registry or an alternative index, and no registry auth.
Why it has not been done
crates.io is effectively universal for open-source Rust. The cases that drive people to a private registry are usually private code, and two mechanisms already cover those:
- git forks, via
git_repo and git_revision on rust_repo
download=, which points a declaration at any target producing a crate tarball, including one built locally
Nobody using the plugin has asked for a registry.
What would change the decision
Somebody needing it. The work is index URL and download URL templating plus auth, which is bounded and unexciting; it is not on the list because there is no consumer, not because it is hard.
Crates come from crates.io. There is no support for a private registry or an alternative index, and no registry auth.
Why it has not been done
crates.io is effectively universal for open-source Rust. The cases that drive people to a private registry are usually private code, and two mechanisms already cover those:
git_repoandgit_revisiononrust_repodownload=, which points a declaration at any target producing a crate tarball, including one built locallyNobody using the plugin has asked for a registry.
What would change the decision
Somebody needing it. The work is index URL and download URL templating plus auth, which is bounded and unexciting; it is not on the list because there is no consumer, not because it is hard.