Source replacement for [dependencies] only but not for [build-dependencies]

#1

I understand that cargo has a feature to replace dependency source to self-hosted: https://doc.rust-lang.org/cargo/reference/source-replacement.html

How do I replace source.crates-io only for [dependencies] but not for [build-dependencies]?

#2

I may be wrong, but at first glance it does not seem possible to have "global" replacements for a category of dependencies but not for another: if you want to "toggle" like that, then you will need to pinpoint the exact dependencies that you want to replace.

What is your use-case?

#3

This is not possible. Currently Cargo has a limitation that it resolves only one set of dependencies used for everything (this has other side effects, such as dev deps adding unwanted features to no_std crates).

1 Like
#4

I'm targeting a special platform, so we maintain a set of modified crates which is only for that platform (https://github.com/mesalock-linux/crates-sgx). However, this is not for building environment (i.e., build dependencies). So we still want to use crates on crates-io for build dependencies. That's the use-case when we want to distinguish dependencies and bulid-dependencies. Thanks!

If a crate is used both by [dependencies] and [build-dependencies], we cannot replace only for [dependencies].

#5

BTW, any GitHub issue of cargo related to this? If no, I’ll submit one to track the progress. (I believe this is a valid feature request.)

#6

Maybe you can use #[cfg(platform)] inside the crate to make it compatible with both environments?