-
Notifications
You must be signed in to change notification settings - Fork 24
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
crankstart cannot be included in a workspace as a git submodule #25
Comments
I'd imagined you'd use crankstart as a dependency from crates, so this would not be an issue. What are you trying to do where you want to include crankstart in your workspace? |
I guess I wanted to put crankstart in the workspace because the instructions for using it include the following entries in Cargo.toml.
Dropping crankstart into the workspace would allow the above path to be used as is. At the time, crankstart and my project workspace were in completely different directories. Since I have a bunch of different things in my workspace, adding crankstart to the mix did not seem unreasonable. The directory structure is a lot like the one in my original post, only there are two libraries. |
Not unreasonable, but I favor leaving it as-it in expectation that it might eventually end up being published to crates.io. |
Are there plans to publish to crates.io? |
Nothing more solid than an expectation. |
Would you be open to help? I would love to assist. |
crankstart is workspace with one member. It cannot, therefore, be included in another Rust workspace as a git submodule. The workaround is to install crankstart and the user workspace in the same directory.
ideal directory structure
workaround directory structure
EDIT: Another workaround is probably to include crankstart as a git submodule and exclude it from the user workspace.
The text was updated successfully, but these errors were encountered: