-
Notifications
You must be signed in to change notification settings - Fork 183
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
Versioning diplomat-tool
through Cargo
#4197
Conversation
1473328
to
3bba7f8
Compare
60edaae
to
521c9a1
Compare
Not a huge fan since diplomat gets reinstalled once every few months, whereas I end up cleaning somewhat regularly because our feature combinations take up disk space, and |
I want to iterate faster than that.
It takes around 10 seconds for a clean build. |
Ah. I feel like it takes longer to build but perhaps that's release mode. That's fine then |
Yeah it takes minutes in release mode, which is why I don't want to keep reinstalling it that way. |
# min version for cargo-make itself). But cargo-make might only be applying | ||
# such dep upgrades defined in the `install_crate` field after the task script | ||
# has run. | ||
[tasks.cargo-make-min-version] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I'd like to keep these around, being able to diplomat-install is still somewhat convenient during debugging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But we don't need diplomat-tool
anymore
This is cleaner than relying on the globally installed
diplomat-tool
being the correct version, and allows for faster iteration.Even after
cargo clean
,cargo run -p diplomat-gen
is faster thancargo install diplomat-tool && diplomat-tool
, and with incremental builds the rebuild is negligible but guarantees the correct version.Uses rust-diplomat/diplomat#348