use cargo-hakari to manage workspace_hack crate

workspace_hack is needed to avoid recompilation when different crates
inside the workspace depend on the same packages but with different
features being enabled. Problem occurs when you build crates separately
one by one. So this is irrelevant to our CI setup because there we build
all binaries at once, but it may be relevant for local development.

this also changes cargo's resolver version to 2
This commit is contained in:
Dmitry Rodionov
2022-03-28 11:39:15 +03:00
committed by Dmitry Rodionov
parent fd78110c2b
commit eee0f51e0c
15 changed files with 96 additions and 45 deletions

View File

@@ -17,3 +17,4 @@ serde = { version = "1.0", features = ["derive"] }
serde_json = "1"
tar = "0.4"
tokio = { version = "1", features = ["macros", "rt", "rt-multi-thread"] }
workspace_hack = { version = "0.1", path = "../workspace_hack" }