On 8/1/14, 3:26 AM, Brad Anderson wrote: > Works fine on Windows for my limited tests. The installer directory issue is resolved. > > I have two issues, the first of which wouldn't require changes to the RC (phew!). The second issue would require a new RC to resolve but could be considered optional. > Let's go ahead and fixing issue #2 for 2.066. We will need to produce another RC anyway: there are at least three other issues that must be addressed and tested prior to the final release. As for issue #1, I have no problems creating the installers as outlined below. I'll build and have them uploaded when I prepare RC2. My problem will stem from knowing when to build D1 in the future because it never really crosses my mind as something that needs to be done. But I'm sure Walter or someone else will alert me when it's necessary to do so. > > First issue: > > As part of the installer revamp I took out D1 and DMC and made separate installer scripts for them which the revamped installer will optionally download and install if the user asks for them. This requires installers for D1 and DMC to be built. It's as simple downloading the latest D1 and DMC zips, extracting them, then running: > > makensis /DEmbedD1Dir=<d1dir> /DVersion1=<d1ver> d1-installer.nsi > > and > > makensis /DEmbedDmcDir=<dmcdir> /DVersionDmc=<dmcver> > dmc-installer.nsi > > And uploading the result to the DigitalMars FTP (at least) and the D download site (ideally). The URLs the D2 installer expects are shown here: > > This would only need to be done once and for every new release of D1 and DMC (which are few and far between). > > I could do this for you and give you a link to download for you to reupload but I think it's probably more appropriate to have it generated by someone with more official standing. If you'd rather I do it just let me know. > > > Second issue: > > I removed the downloading of Curl from the installer with the goal that we switch to just having it embedded with the rest. The release builder script makes use of Nick's localextras zip. If my understanding is correct we could just add curl to that zip and it'd get included in the release. It's up to you whether to fix this for 2.066 or to just include it in 2.067. In the meantime, end users could just do what they used to do to get curl: download and extract the curl zip on the download page into the installation folder. > > > On Thu, Jul 31, 2014 at 6:51 AM, Andrew Edwards via dmd-beta <dmd-beta@puremagic.com <mailto:dmd- beta@pu remagic. com>> wrote: > > DMD v2.066.0-rc1 binaries are available for testing: > > http:// wiki.dl ang.org/ Beta_Testing > ____________ ____________ ____________ ___________ > dmd-beta mailing list > dmd-beta@puremagic.com <mailto:dmd- beta@pure magic.com> > http:// lists. puremagic.com/ mailman/ listinfo/ dmd-beta > > First issue:As part of the installer revamp I took out D1 and DMC and made separate installer scripts for them which the revamped installer will optionally download and install if the user asks for them. This requires installers for D1 and DMC to be built. It's as simple downloading the latest D1 and DMC zips, extracting them, then running:makensis /DEmbedD1Dir= /DVersion1= d1-installer.nsiandmakensis /DEmbedDmcDir= /DVersionDmc= dmc-installer.nsiAnd uploading the result to the DigitalMars FTP (at least) and the D download site (ideally). The URLs the D2 installer expects are shown here: https:// github.com/ D-Programming- Language/ installer/ blob/master/ windows/ d2-installer. nsi#L66 This would only need to be done once and for every new release of D1 and DMC (which are few and far between).I could do this for you and give you a link to download for you to reupload but I think it's probably more appropriate to have it generated by someone with more official standing. If you'd rather I do it just let me know.Second issue:I removed the downloading of Curl from the installer with the goal that we switch to just having it embedded with the rest. The release builder script makes use of Nick's localextras zip. If my understanding is correct we could just add curl to that zip and it'd get included in the release. It's up to you whether to fix this for 2.066 or to just include it in 2.067. In the meantime, end users could just do what they used to do to get curl: download and extract the curl zip on the download page into the installation folder.On Thu, Jul 31, 2014 at 6:51 AM, Andrew Edwards via dmd-beta