-
Notifications
You must be signed in to change notification settings - Fork 99
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
Support workspace dependencies #113
Comments
Just to start a discussion on this, since we are running into this at Prisma and we want to start using crane. I tried using crane with a repo with workspace dependencies. In the repo itself, no problem. It looks like cargo transparently does the job. In another repo that depends on the repo with workspace dependencies via git, here's what we get:
I interpret this as cargo looking for the workspace I'm not super familiar with crane internals, so it may not be a good idea, but could the fix be as simple as detecting which crates use workspace dependencies in |
@tomhoule could you provide a flake.nix with which I can reproduce the issue? (bonus points if it's a minimal setup) |
Wonder if this is an issue with We don't use |
Here's the minimal setup: https://github.com/tomhoule/crane-workspace-deps-repro — it depends on a large workspace so it takes a while to vendor the dependencies but it's minimal otherwise. I expect the result would be the same replacing the dependency on |
same issue
So we If there will be donated button in crypto can donate the equivalent of 42 USD for fix. |
We use latest crane git commit. |
There's progress on the |
Rust 1.64 supports declaring cargo dependencies at the workspace level. We should take those into account when vendoring crates
https://blog.rust-lang.org/2022/09/22/Rust-1.64.0.html
The text was updated successfully, but these errors were encountered: