FS#291 — Include hg hash/version number if available in build and print it out when executing
Attached to Project— M5 Bugs
Opened by Ali Saidi (saidi) - Wednesday, 29 August 2007, 02:46PM
Last edited by Ali Saidi (saidi) - Friday, 11 April 2008, 01:48PM
Opened by Ali Saidi (saidi) - Wednesday, 29 August 2007, 02:46PM
Last edited by Ali Saidi (saidi) - Friday, 11 April 2008, 01:48PM
| Minor Enhancement | |
| Global/Other | |
| New | |
| No-one | |
| All |
| High | |
| Normal | |
| 2.0beta3 | |
| Undecided | |
| Undecided | |
![]() |
I think this is almost a must have when we release the source code to the world. If we get a random bit of output this is a good way to know what version it came from. Perhaps we want both current version and last upstream version although I don't exactly know how that could be found.
Additionally, there have been a couple of times when I wanted to know what version this particular binary came from
Additionally, there have been a couple of times when I wanted to know what version this particular binary came from
This task depends upon
This task blocks these from closing

I've attached code adds a hg version string. Problem is if the hg version changes (even if there are no other changes, e.g. you create a commit) you have to rebuild. Nate doesn't like that and I don't know of a way to fix it.