On 1/23/14, 7:25 PM, vitaly_m wrote:
> On Tuesday, 21 January 2014 at 22:22:01 UTC, Andrew Edwards wrote:
>> For a description of these packages, visit
>> http://dlang.org/downloads.html.
>
> The link should be http://dlang.org/download.html (no 's' before
> .html)

Thanks

On Thursday, 23 January 2014 at 23:44:09 UTC, Jordi Sayol wrote:
> El 24/01/14 00:24, Brad Anderson ha escrit:
>> On Thursday, 23 January 2014 at 13:29:31 UTC, Martin Nowak wrote:
>>> On Thursday, 23 January 2014 at 06:50:47 UTC, Brad Anderson wrote:
>>>> This of course is relying on the zip file getting uploaded to
>>>> downloads.dlang.org.  You could use the digitalmars urls for
>>>> betas, I suppose, since those don't end up on the download site
>>>> anyway.  The url template is just a bit further down in the file.
>>>
>>> Please no manual steps. Is it possible to do this in the nsi script?
>> 
>> Well, presumably Andrew will get access to upload to the download site at some point soon and he's just use that instead of digitalmars's FTP and this won't be a problem.
>> 
>> The NSIS script already requires a bit of manual editing (basically just updating the version number). I think I can probably figure out a way to do away with that though (NSIS can pull definitions from a separate file and the NSIS command line supports specifying definitions). I'll experiment with these soon and see what I can do to allow it to be completely automated.
>> 
>
> You can take a look on linux/win/installer.nsi that get version argument from linux/dmd_win.sh and therefore from command line.
> 

Ok, cool.  I'll take a look there.

Am 23.01.2014 10:38, schrieb Walter Bright:
> On 1/22/2014 5:37 AM, Sönke Ludwig wrote:
>> (...)
>>
>> There is also a build issue that sometimes occurred at the same place
>> in 2.064
>> in the form of template instantiation failures and now produces linker
>> errors:
>> https://github.com/rejectedsoftware/vibe.d/issues/458
>
> Did you try the -allinst flag?

Tried it, but it didn't make a difference. I'm running Dustmite on it now, but that will take a while to complete.

>
>>
>> Finally, I'm getting some "recursive alias" errors that I managed to
>> circumvent
>> in previous releases.
>>
>> I'm going to run dustmite on these two and create bugzilla issues.

Unfortunately, in case of the recursive alias error, Dustmite reduced to a case that fails for both, 2.065 and 2.064. Also, every little change from there either fixes the error or makes it appear again. This is obviously stabbing too deep in unspecified language territory. I gave up on it and am now in the process of completely rewriting the affected code.

On 01/24/2014 12:24 AM, Brad Anderson wrote:
>
> The NSIS script already requires a bit of manual editing (basically just
> updating the version number). I think I can probably figure out a way to
> do away with that though (NSIS can pull definitions from a separate file
> and the NSIS command line supports specifying definitions). I'll
> experiment with these soon and see what I can do to allow it to be
> completely automated.

Sounds great, my mid term goal is to integrate all the package/installer scripts with the vagrant setup and to build them using local dmd.zip folders.

On 01/23/2014 01:44 PM, Martin Nowak wrote:
>> 1) The link for nsisunz.zip per readme.txt does not work.
>
> I wrote the author of the plugin.

He no longer has posses this file.
@Brad Anderson, maybe you or Walter still have a download laying around?

On 1/24/14, 9:17 AM, Martin Nowak wrote:
> On 01/23/2014 01:44 PM, Martin Nowak wrote:
>>> 1) The link for nsisunz.zip per readme.txt does not work.
>>
>> I wrote the author of the plugin.
>
> He no longer has posses this file.
> @Brad Anderson, maybe you or Walter still have a download laying around?


Martin, there is no need. I included a link to where I found the copy I am using. What might need to be done is a copy stored on the server but my main point was that the readme file need to be updated.

Could you please make a "2.065.b1" tag on the GitHub as well so we finally start using the release naming scheme you mentioned in the previous beta-release thread here on the NG?

On 1/24/14, 10:04 AM, Dejan Lekic wrote:
>
> Could you please make a "2.065.b1" tag on the GitHub as well so we
> finally start using the release naming scheme you mentioned in the
> previous beta-release thread here on the NG?


2.065.b1 is not going to work for FreeBSD and Debian OSes. The tags will be in the form: 2.65.0-b1. Hope that doesn't mess with your scripts too much. I will not be uploading one for beta 1 since I will be building beta 2 tonight.

On Friday, 24 January 2014 at 19:58:22 UTC, Andrew Edwards wrote:
> On 1/24/14, 10:04 AM, Dejan Lekic wrote:
>>
>> Could you please make a "2.065.b1" tag on the GitHub as well so we
>> finally start using the release naming scheme you mentioned in the
>> previous beta-release thread here on the NG?
>
>
> 2.065.b1 is not going to work for FreeBSD and Debian OSes. The tags will be in the form: 2.65.0-b1. Hope that doesn't mess with your scripts too much. I will not be uploading one for beta 1 since I will be building beta 2 tonight.

I was eager to try the beta2 on my debian, but it seems things
didn't turned out to work yesterday.

"Martin Nowak"  wrote in message news:jcszzsgkwldowcmwzooa@forum.dlang.org...
> Mmh, we could simply upload the intermediate zip files for each platform, that fall out of create_dmd_release before they are combined.

Any ETA on this?  I'd like to provide a win32 version with dmd replaced by ddmd for people to test.