On Tuesday, 28 May 2013 at 04:12:06 UTC, Walter Bright wrote:
On 5/27/2013 7:44 PM, Brad Anderson wrote:
(Sorry for the NG noise, I would have just emailed you
directly about this but I
couldn't manage to find your email address)
Could you use the AWS hosted URLs for the zip files in the
windows installer
script? It takes around 5-10 minutes to install from the
ftp.digitalmars.com URLs.
Thanks.
Pull requests are welcome!
https://github.com/D-Programming-Language/installer
I know, I've made about 6 of them so far :)
I just mean when you update the .nsi with the URLs to the new
release <http://goo.gl/BBUXb> during your regular release
process, use the S3 hosting URLs instead of the
ftp.digitalmars.com address to the 2.063 zip.
I've gone ahead and made a pull request using the dmd.2.062.zip
url as a base but I'm not entirely sure if other parts of the S3
url will change over time ("2013" in the URL suggests that at
least would).
https://github.com/D-Programming-Language/installer/pull/16
While we are on the subject, I'm thinking of doing a pull request
to make it so the installer executable is something more along
the lines of "dmd-2.063.exe". Reusing dinstaller.exe over and
over is confusing (to me at least). You wouldn't have to do
anything, it'd just use the version string in the .nsi you update
when you roll a release.
Also, I'd like to make a pull request to move away from a
internet installer and just package it all into the installer
executable. One benefit is it shouldn't be hard for NSIS to only
have it grab the Windows specific stuff. It'd just grab some
wildcarded paths (dmd2/{html,src,windows} I believe is all that
is required). The most you'd have to do is give it a path to the
root of the directory you make the dmd zip from (probably dmc and
d1 too). NSIS would do the rest (and LZMA compress it so it'll
be even smaller).
