Cargo.toml points directly to directories that don't exist about juice HOT 6 CLOSED

I am aware of this shortcoming and will deal with this ASAP, but note that no earlier than CI can handle it properly.

[patch.crates-io]
coaster = { path = "../coaster" }                                                                       

Background:
Last time I checked cargo was just about to release the [path.registry] feature.

from juice.

I think the way to go is to use the actual releases from crates.io rather than git repositories, but I am happy for feedback on that, @canndrew .

from juice.

The patch command is working well for local development, but very tedious to inject into CI, so I am looking into https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#overriding-with-local-dependencies respectively https://doc.rust-lang.org/cargo/reference/config.html on how to implement this with less friction.

from juice.

Yeah, I'm not aware of any easy way to keep a bunch of separate projects which depend on each other in-sync. 😕

from juice.

So I have something in place, but I have yet to test and deploy ci accordingly.

from juice.

The workspace approach and mergeing of repos should have resolved this issue now once and for all, feel free to re-open if needed.

from juice.