cargo-specification
cargo-specification copied to clipboard
rebrand
from str4d:
Binaries named cargo-foo do not look language-agnostic, as that naming specifically is for integration with cargo as cargo foo
we should probably rename cargo-spec to something else, and remove the dependency on cargo so we can release binaries
https://github.com/marketplace/actions/rust-release-binary
Just a thought on this... I found this because I was looking for spec tools to add to my cargo toolbox. I prefer the tools I use to be integrated. If you do break ties with Cargo, would you consider adding an optional Cargo integration?
I think that's fine, but in general this tool seeks to be language agnostic so I don't think it makes sense to have the main binary be a cargo tool : o (in any case this is low on the list of priorities