[dmd-beta] Changes to v2.066.0
David Nadlinger via dmd-beta
dmd-beta at puremagic.com
Sat Sep 6 08:37:43 PDT 2014
I think I know what is going on now. The source of the problem seems to
be a bug in your Portfile, and not an issue on our side.
I'm not familiar with how the GitHub handling works exactly, but
---
github.setup D-Programming-Language dmd 2.066
---
seems to suggest that it fetches the "2.066" branch. This is not a good
idea, because further point releases are also prepared there, as Kenji
already mentioned. Instead, please use the actual release tag, e.g.
"v2.066.0".
Best,
David
On 6 Sep 2014, at 10:24, Takeshi Enomoto via dmd-beta wrote:
> Dear DMD developers,
>
> Thank you for developing DMD.
> I maintain dmd and related packages of MacPorts.
>
> We noticed a few updates to v2.066.0 of dmd, druntime and phobos
> without changing their tags in the git repository (releases).
>
> <https://github.com/D-Programming-Language/dmd/releases>
>
> We call such updates `stealth updates'.
> The checksums are verified to make sure that the correct source code
> have been downloaded by MacPorts' port command.
> The checksums are written in the package description file, called
> Portfile.
> We need to special treatment for stealth updates.
>
> <https://trac.macports.org/wiki/PortfileRecipes#stealth-updates>
>
> From the viewpoint of package maintainer,
> stealth updates are not a good idea.
> I understand that the changes are for bug fixes or enhancement.
> But if so a new version number (e.g. v2.066.1 or v2.066.0.1)
> or a tag should be given to the commit.
>
> I appreciate if you discussed my suggestion among the developers and
> considered adopting it.
>
> Regards,
>
> Takeshi
>
> -----
> Takeshi Enomoto
> takeshi at macports.org
More information about the dmd-beta
mailing list