Seconding some of the points of Patrick's September 11, 2015 post: > > is 0.32 the correct number? The current development version is 0.33; > or do you use some kind of backport strategy? > I personally would prefer naming the new release branch "release-0.33", with a tag of "ghdl-0.33rc1"
I.e., I think abandoning the current 0.32rc1 and skipping a release number would be *less* confusing than having a repo history of 0.33dev=>0.32rc2 overwriting the 0.32dev=>0.32rc1 branch already started. It would also be more consistent with the release flow outlined here (ignoring the specific #'s currently on that page): http://sourceforge.net/p/ghdl-updates/wiki/Release/ > > Shall I create an install script, which is embedded into the zip file? > > Possible tasks for such a script: > - Install (copy into a destination folder; register in PATH) > - Uninstall (delete folder) > - Update (remove old files, copy new files) > > I think NSIS support is not needed any more. I also looked into WIX (Windows > Installer XML), it's nice but a bit too complex for just doing xcopy > deployment. > I would also vote for avoiding an installer executable. The simple unzip-and-run-batch-files installation process I had done for the ghdl-0.31-mcode-win32 distribution seems to have worked very well: 1) There have been thousands of 0.31 downloads, and no(?) questions about 0.31 Windows install problems 2) A simple copy-and-set-path batch file can be done *without* admin privileges (important for situations like student labs) 3) The NSIS installer is known to corrupt long Windows paths, see Ticket 10 Another thing to think about is how to reorganize the wiki so as to preserve the existing 0.31 build/install instructions, along with updating the wiki pages for 0.32 -Brian Davis _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
