Commit Graph

8 Commits (16d8ae5e04b18bc41101546b0a618f5b5d8d0e7a)

Author SHA1 Message Date
Carol (Nichols || Goulding) 76909b07e4
fix: Exclude optional object-store implementation crates from cargo-hakari
Aha! cargo-hakari turns on all features, but usually in development all
the specific object storage implementation crates are off.

Excluding them in the hakari config reduces the workspace crate a bit.

Connects to #3117.
2021-12-06 09:37:15 -05:00
Carol (Nichols || Goulding) ddc1504135
fix: Exclude influxdb2_client from the workspace hack crate
This enables the removal of the futures and futures-io crates.

Connects to #3117.
2021-12-06 09:37:14 -05:00
Carol (Nichols || Goulding) cf6286364e
fix: Exclude criterion from hakari analysis
Connects to #3117.

Criterion builds clap without default features, which causes clap to be
listed in the workspace hack crate with its default features. In
general, actually building criterion will be rare (and we should move
all benches to separate crates that can be excluded) so it should be
fine to rebuild clap when building benchmarks anyway.
2021-12-06 09:36:50 -05:00
Carol (Nichols || Goulding) 0fda9608d8
fix: Exclude optional pprof crate from workspace-hack 2021-12-06 09:36:32 -05:00
Carol (Nichols || Goulding) f3c814e091
fix: Exclude crates conductor depends on from workspace hack 2021-11-22 11:55:38 -05:00
Carol (Nichols || Goulding) a6908f1613
fix: Exclude tikv-jemalloc-sys from workspace hack as it's mutually exclusive with heappy 2021-11-19 13:46:17 -05:00
Carol (Nichols || Goulding) 2f452268af
fix: Exclude some bench/test crates from the workspace hack 2021-11-19 13:38:27 -05:00
Carol (Nichols || Goulding) f66cd681c2
feat: Results of using cargo hakari init workspace-hack 2021-11-19 09:20:35 -05:00