Stamps are nice, but git and friends miss something that the VCS of yore would give you - a monotonously increasing number you could stick somewhere in your version - and be able to tell at a glance which was newer.
2.4.16-12 vs 2.4.16-35 - obviously -35 is later.
But 2.4.16-bcbd1c6 vs 2.4.16-d645104 - which is later? Compile dates won't necessarily help because "earlier" code could have been compiled later.
It's forcing the versioning to do something it shouldn't, arguably, but is nice to have something that the user can decipher (even if you still should have the commit).
planteur 25 days ago [-]
The blog post mentions `git describe`, which includes the revision number (since last annotated tag), e.g. "4.25-23-g98f23f54".
sgbeal 26 days ago [-]
> --moreversion
Suggestion: more conventional and intuitive would be: --version --verbose
bombcar 25 days ago [-]
I took it to be more like "The answer? Use --version. And if that don't work, use --moreversion."
Most commercial software gives you a detailed version report.
Either way, the simplest solution would be -v, and -vv and -vvv … don’t do moreversion or lessversion.
The equivalent would be —version —version —version.
ploution 26 days ago [-]
The version seems to be the number one information in order to avoid making things worse! Not all solutions apply to all versions of a running product.
sourcegrift 25 days ago [-]
Great post! I propose all programs have a `--version` flag. Anything similar for Rust + Cargo right now?
sourcegrift 25 days ago [-]
I meant `--stamp` lol
sourcegrift 25 days ago [-]
Dang please mark this post for boosting?
Rendered at 14:25:19 GMT+0000 (Coordinated Universal Time) with Vercel.
2.4.16-12 vs 2.4.16-35 - obviously -35 is later.
But 2.4.16-bcbd1c6 vs 2.4.16-d645104 - which is later? Compile dates won't necessarily help because "earlier" code could have been compiled later.
It's forcing the versioning to do something it shouldn't, arguably, but is nice to have something that the user can decipher (even if you still should have the commit).
Suggestion: more conventional and intuitive would be: --version --verbose
https://www.youtube.com/watch?v=SNgNBsCI4EA
Most commercial software gives you a detailed version report.
Either way, the simplest solution would be -v, and -vv and -vvv … don’t do moreversion or lessversion.
The equivalent would be —version —version —version.