-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
semver binary #100
Comments
Issue #100! YAY! 😄 |
I would not mind including it here! This would be useful. |
Cool! |
Hmm, I didn't think of Cargo.toml dependencies, it turns out, cargo does not yet support binary-only dependencies (rust-lang/cargo#1982), which is unfortunate, because you'd get them in library-only use but not use them.... Anyways, I'll first write it, then we can decide what :) |
Here is a first prototype: |
Pull request: #101. |
I updated the semver-parser (made common public: steveklabnik/semver-parser#13) but I think you should take a look first. Here is "working" version of semver: https://github.com/lunemec/semver/tree/binary I didn't create PR because semver-parser with version 0.7.1 doesn't exist. I tested it against my github fork with changes, and everything works fine. Now the dependencies only contain clap without default features, that means these libraries (from clap alone): [dependencies] I'm not sure if that is OK with you or not. If not, I suggest creating another project semver-bin where these dependencies can be. Thanks! |
/cc @steveklabnik |
Yeah, still thinking, sorry! |
I would prefer not to build this into this crate. It seems appropriate for a separate standalone project though! |
Hello,
I ran into a problem with my CI scripts needing to be bumped by 1 minor version + added a -ci at the end. I couldn't find any "easy" way to do it in bash (except for some crazy AWK scripts which didn't work).
I wanted to write this binary in rust, but since most of the work is done here, I just wanted to ask if you'd be opposed to me writing a binary version to semver (which could be included, or as separate project).
The idea is following:
The main usage is for gitlab CI/CD scripts, which need to parse previous program version, and deploy +CI version in metadata. Since I have multiple programming environments, each uses diferent tools to manage versions and some (docker) don't have any.
I wanted to start rust-semver project on my github profile, but I didn't want to rip-off this project (since it will do most of the work).
Thank you!
The text was updated successfully, but these errors were encountered: