Zero3 has been working on a simple, fast windows-specific installer using AutoHotKey. AHK is GPL, runs well under Wine according to winehq, and has a command-line compiler. Wine can be built without the X libraries and does not need root privelidges. So this can be done under a single restricted user. However, if we go for the full bundle approach, we would need to trigger a rebuild of the windows installer after successfully deploying a new stable jar. This does NOT necessarily mean running it under the user that builds the main jars: a simple protocol involving creating files and waiting for inotify will probably suffice (something similar happens already with the jars and the website).
First, are there any unresolvable security issues? And do they specifically relate to bundling? Second, is this a good idea in any case? Advantages: - Probably a smaller download. - Can transparently auto-download Java if needed (unless proxy settings are required, in which case Freenet itself probably won't work). - Much more control over the install process, so we can have far fewer steps where the user has to click "Next", especially if we go for a bundle-installer. - Since we're moving all the config into the post-install wizard, there should be very little maintenance required. Disadvantages: - Have to do some work on emu. - Very few of the developers run Windows, or are familiar with AHK, so if we DO need to change this, it will be a little problematic. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20081211/2501613d/attachment.pgp>
