NSIS 3.0 is out for a while and there are MSYS2 packages for NSIS 3.x which would make the release process on Windows easier.
@eht16 is this gonna be your last minute windows change for 1.30 or should we move the milestone to 1.31? :wink:
As tempting as it is, I think I can resist this time :).
@eht16 What about this?
We should still port the installer to NSIS 3. This would also ease creating full installers from the nightly builds as NSIS 3 is available as Debian package (not tested but might work to build full installers from nightly builds).
Though it is unlikely I will work on this myself in the next months.
@eht16 should I move that to 1.35 milestone?
Did it myself, thanks for reminding me.
Once more? :)
Just move it to Geany 5.0 :-P
Come on, this is only 2.5 years old :)
I still like to get this done (not necessarily by myself) as then we can build the installer from within the MSYS2 environment which eases the release process. And it might even help to cross-build the installer in some more far future.
Sound great, but I'll still move it one milestone forward :)
@b4n I know you didn't believe this will ever happen but here we are: #2181.
The migration of the installer script was way easier than expected, I just had to start doing it :). As a bonus, I added a script to update the keywords in the NSIS filetype definition.
Sometime before 1.36, I will update the G-P installer as well.
Closed #1302 via #2181.
github-comments@lists.geany.org