← Back to index | Original Bugzilla link

Bug 12229 – Properly name DMD compiler versions

Status
RESOLVED
Resolution
WONTFIX
Severity
normal
Priority
P2
Component
installer
Product
D
Version
D2
Platform
All
OS
All
Creation time
2014-02-22T20:13:02Z
Last change time
2018-03-27T07:57:25Z
Assigned to
No Owner
Creator
Andrew Edwards

Comments

Comment #0 by edwards.ac — 2014-02-22T20:13:02Z
On 02/20/2014 02:13 AM, Andrew Edwards wrote: Regardless of which version of DMD one ends up using, the DMD help message only displays the base release version. Meaning, if I'm running beta 1, 2, 3 or rc 1 of release 2.065, typing dmd at the shell prompt always yields "DMD[32/64] D Compiler v2.065". It must be possible to change this so that the correct version information is displayed. If I'm running beta 1, it should say "DMD[32/64] D Compiler v2.065 beta 1" and the same goes for any other release. On 2/20/14, 2:03 PM, Walter Bright wrote: The string printed is set by the variable global.version, which is set in Global::init() by the contents of verstr.h.
Comment #1 by code — 2014-02-23T07:34:54Z
Version number is set by the version file. https://github.com/D-Programming-Language/dmd/blob/master/VERSION We should remove that file because it requires manual updating. Instead we can set the version from the build script.
Comment #2 by edwards.ac — 2014-02-27T21:48:44Z
We should indeed remove VERSION from the repo. At no time should HEAD be tagged with a specific version number. This creates confusion when trying to identify between changes intended for master vs. the branch and unnecessarily complicates the pick process.
Comment #3 by greensunny12 — 2018-03-27T07:57:25Z
> We should indeed remove VERSION from the repo See e.g. https://github.com/dlang/dmd/pull/6935 tl;dr: VERSION needs to be kept in the source tree e.g. in case someone downloads the source tarball from GitHub. -> closing this as WONTFIX