> Neat, but, if anyone can build it, can they run it to see if it works?
As long as you don't expect a GUI :). Seriously, my build script executes the generated installer via Wine, installs Geany, then execute `wine geany --version` to check it is properly installed and can be executed and then uninstall Geany again and check there is nothing left. This is at least some rudimentary testing to get sure all necessary DLLs are included. I didn't try but it should be possible to fully run Geany via Wine. > With Geany-plugins, I wonder it it would be better to just include it in the > one install, I would expect (but have no evidence) that most people will > install them if they realise they exist. Tempting idea. It certainly would be a benefit for users. On the contrary the installer size would be even bigger (not sure how much this is an issue nowadays). But it would increase the burden to make releases of Geany and Geany-Plugins independently of each other. Also it would make the build script and NSIS installer quite big and complex. So, I would keep Geany and G-P builds separated. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2592#issuecomment-698576003
