-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using workspaces with small closures #270
Comments
For additional context, I tried using the |
I see - maybe
Whoopsie, yeah - looks like it 😅 |
Hmm, doesn't look like it works as one might expect. Cargo still tries to find the specific workspace members. I'm not sure you can override it like that, cargo still uses the root Cargo.toml to determine the workspace members. |
Background
I have a repository setup as such:
The root
Cargo.toml
establishes a workspace as such:Then packages are built as such:
Problem
The above derivation captures the entire repository (because of
inputs.self
). Thus, when anything in the repository changes, the input hash changes and causes a rebuild of any of the packages.If I filter
root
to only include the source of a single package, cargo fails because it expects all packages defined in the workspace to exist on the filesystem. For example, if I filter only to includesrc/pkg1
, it fails with:This creates a problematic setup because I cannot disassociate the projects such that changes in one do not invalidate another one. I imagine I must be doing something wrong here. Is there a way to isolate workspace packages to avoid this problem?
The text was updated successfully, but these errors were encountered: