cargo_metadata and regex are pretty heavy dependencies which AFAICT are only used for VERGEN_CARGO_DEPENDENCIES. If I want to get only say VERGEN_CARGO_FEATURES out of the "cargo" feature, I am also downloading and compiling a decent amount of transitive dependencies which are unused if I don't have them in the dependency graph already.
If they are in the dependency graph already, they will be compiled twice when building for release as build dependencies always get built with the dev/debug profile.
If you think a separate feature for this is worth it, or a different idea, I would be happy to implement it.
cargo_metadata and regex are pretty heavy dependencies which AFAICT are only used for
VERGEN_CARGO_DEPENDENCIES. If I want to get only sayVERGEN_CARGO_FEATURESout of the "cargo" feature, I am also downloading and compiling a decent amount of transitive dependencies which are unused if I don't have them in the dependency graph already.If they are in the dependency graph already, they will be compiled twice when building for release as build dependencies always get built with the dev/debug profile.
If you think a separate feature for this is worth it, or a different idea, I would be happy to implement it.