-
Notifications
You must be signed in to change notification settings - Fork 73
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
Version string is always the same even across forks! #75
Comments
If you can tell me how to do it (in an easy and simple way), I'll be happy to oblige. |
@gatopeich ping? This seems to be a useful feature, but I don't have enough of Git and toolchain experience to know how to do that. So, recommendations are welcome. A PR would be even better. |
Just edit first line in root dir configure.ac: With a bit of time we could add commit hash to the version string which I usually do, but this suffices for my needs 🙂 |
Even better (untested):
This produces version "v0.9.28-951-ga6376b40/mouse07410/vlm_master" for me, but "mouse07410/vlm_master" should come from |
Sorry to say, the above does not work.
This does not work either:
And in the log:
|
@gatopeich perhaps you'd like to submit a PR? |
I'd love to, but I am terribly busy :-( |
I hate to admit it, but I'm also quite busy - and the proposed change is outside of my area of expertise/experience. :-( |
I have been testing a few forks and branches of
asn1c
and it was quite confusing to distinguish which binary I am running, since they all spit the same version"ASN.1 Compiler, v0.9.29"
It would make sense to include a reference to the repo name, branch and latest commit:
The text was updated successfully, but these errors were encountered: