[Issue 15910] Prevent mismatch of VERSION information in dmd releases

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15910 Iain Buclaw changed: What|Removed |Added Priority|P1 |P4 --

[Issue 15910] Prevent mismatch of VERSION information in dmd releases

2018-03-27 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15910 Seb changed: What|Removed |Added CC||greensunn...@gmail.com ---

[Issue 15910] Prevent mismatch of VERSION information in dmd releases

2017-06-04 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15910 --- Comment #5 from Joseph Rushton Wakeling --- Note that with the DMD backend now open sourced, this is going to have a greater impact: unless it's addressed, every downstream packager will have to implement a manual

[Issue 15910] Prevent mismatch of VERSION information in dmd releases

2016-05-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15910 John Colvin changed: What|Removed |Added CC|

[Issue 15910] Prevent mismatch of VERSION information in dmd releases

2016-04-13 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15910 --- Comment #3 from Joseph Rushton Wakeling --- Unfortunately, the proposed workaround didn't work for me when I tried it. If when trying to build phobos I use, make -f posix.mak VERSION=2.071 then I wind up with

[Issue 15910] Prevent mismatch of VERSION information in dmd releases

2016-04-11 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15910 --- Comment #2 from Joseph Rushton Wakeling --- > That's not entirely correct b/c the downloadable packages contain the correct > VERSION file Well, yes, that's really the point of concern -- there is a mismatch

[Issue 15910] Prevent mismatch of VERSION information in dmd releases

2016-04-10 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15910 Martin Nowak changed: What|Removed |Added CC||c...@dawg.eu --- Comment #1