On Tue, Sep 20, 2005 at 05:56:45PM +0100, Neil Mitchell wrote:
I propose that either:
1) The tools used to make the current installer .msi files make themselves known to the world, along with appropriate documentation and scripts.
2) I (or someone else) writes an MSI file generator, probably using the free Wix toolset.
3) I (or someone else) writes an NSIS installer, which is an .exe installer based on the NSIS toolkit, Google seems to now use this as their preferred installer setup, so it can't be too bad.
4) I (or someone else) writes an installer from the ground up. Its not that much work, as I already have about 98% of the code from writing an installer from the Pingus project. The installer is a simple cat installer.exe data.zip > winhugs.exe installer, so it allows making an easy distribution from a zip file, even under Linux.
I had a play with NSIS a while ago. It seems to be short on tutorial material, but the basics are fairly simple, except that I couldn't get it to work (failed while installing). NSIS seems do do more than a cat would.