Cargo workspace; but every package retains a cargo.lock


I’m trying to work around a couple issues (namely My use case is this:

I have several different rust binaries in a single VSCode/Atom project (think of them like microservices). In order to get RLS working for all those project they must all reside in a cargo workspace. A feature of cargo workspaces is that a single Cargo.lock is generated. However outside of my development machine these binaries all live in different repositories, (all with different CI pipelines) and each repository must retain it’s own Cargo.lock.

I can’t think of a good way to work around this issue. Does anyone else have any ideas?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.