On 2017-06-05 23:38, Joseph Rushton Wakeling wrote:
Yup, my instinct is that if a VERSION file needs to exist at all it
should be created during the build process out of `git describe` output.
It's used by DMD to build the version, that is, the output of "dmd
--version". The content of the
On Monday, 5 June 2017 at 18:25:19 UTC, Martin Nowak wrote:
IMO the problem here is the usage of a VERSION file in the
first place, which exists only b/c it's somewhat tricky to
invoke git on Windows.
Yup, my instinct is that if a VERSION file needs to exist at all
it should be created
On Saturday, 3 June 2017 at 19:57:36 UTC, Joseph Rushton Wakeling
wrote:
The problem here is that anyone downstream wanting to build or
package from source has to work around this issue, that without
manual intervention, the version information of the compiler
will be incorrect.
If that's
On Saturday, 3 June 2017 at 18:08:40 UTC, Joseph Rushton Wakeling
wrote:
On Thursday, 1 June 2017 at 21:04:00 UTC, Martin Nowak wrote:
This point release fixes a few issues over 2.074.0, see the
changelog for more details.
I'm afraid that the release has another fault: the VERSION file
still
On Friday, 2 June 2017 at 09:52:45 UTC, Joseph Rushton Wakeling
wrote:
Great news, thanks Martin. I'll update the snap packages over
the weekend. :-)
Done.
sudo snap refresh --classic --edge dmd
should upgrade things for anyone who already has the package
install; otherwise,
sudo
On Saturday, 3 June 2017 at 21:17:18 UTC, Seb wrote:
I understand the problem, but there's only so much Martin can
do in his free time.
I'm not asking anyone to do the work. I'm asking for a clear
recognition that this is a problem that should be fixed. I'm
also asking for a clear
On Saturday, 3 June 2017 at 19:57:36 UTC, Joseph Rushton Wakeling
wrote:
It's a mistake that remains tolerated, despite the problem
being known and having an associated issue, because the
dlang/installer scripts work around it, meaning the fundamental
problem never gets fixed.
I understand
On Saturday, 3 June 2017 at 19:31:51 UTC, Seb wrote:
Tags are only made from the stable branch.
The point is that the VERSION file is wrong in the officially
tagged release source.
Well, as mentioned minor point releases have never been changed
in the git repo before:
On Saturday, 3 June 2017 at 19:02:36 UTC, Joseph Rushton Wakeling
wrote:
On Saturday, 3 June 2017 at 18:42:57 UTC, Seb wrote:
So, I guess your problem is the VERSION file on the dmd stable
branch?
No, it's the VERSION file present if one checks out the
v2.074.1 tag.
Tags are only made from
On Saturday, 3 June 2017 at 19:02:36 UTC, Joseph Rushton Wakeling
wrote:
The point is here that this keeps happening.
The relevant issue (filed over a year ago):
https://issues.dlang.org/show_bug.cgi?id=15910
On Saturday, 3 June 2017 at 18:42:57 UTC, Seb wrote:
So, I guess your problem is the VERSION file on the dmd stable
branch?
No, it's the VERSION file present if one checks out the v2.074.1
tag.
I suspect this doesn't show up in the official packages because
IIRC the VERSION file is edited
On Thursday, 1 June 2017 at 21:04:00 UTC, Martin Nowak wrote:
This point release fixes a few issues over 2.074.0, see the
changelog for more details.
I'm afraid that the release has another fault: the VERSION file
still gives 2.074.0. This means that unless it is edited during
the build
On 2017-06-01 23:04, Martin Nowak wrote:
Glad to announce D 2.074.1.
http://dlang.org/download.html
This point release fixes a few issues over 2.074.0, see the changelog
for more details.
http://dlang.org/changelog/2.074.1.html
Any progress on the remaining regressions [1]?
[1]
On Thursday, 1 June 2017 at 21:04:00 UTC, Martin Nowak wrote:
Glad to announce D 2.074.1.
http://dlang.org/download.html
This point release fixes a few issues over 2.074.0, see the
changelog for more details.
http://dlang.org/changelog/2.074.1.html
Great news, thanks Martin. I'll update
14 matches
Mail list logo
