Hi, On 02-11-17 09:31, Samuli Seppänen wrote: > On 01/11/2017 20:46, Simon Rozman wrote: >>> Speaking of MSIs... we are planning on moving from NSIS to MSI due to >>> security issues like the one we fixed in previous release. At the moment >>> four >>> (other) people who have expressed interest in taking part in the "create MSI >>> installers for OpenVPN" project. One of these people is me. >>> >>> Would you be interested in joining forces in this task? >> >> I'd love to. Count me in! > > Excellent! > >> I have been in the MSI packaging for about 10 years now - automated builds >> from command line, developed DLL custom actions in C/C++, localization, GUI, >> WiX etc. > > As you probably know, right now we produce Windows executables and > installers on Linux using openvpn-build: > > <https://github.com/OpenVPN/openvpn-build> > > It seems that WiX which you mention would probably be our tool of > choice, given it is open source (MS-RL): > > <https://github.com/wixtoolset/wix3> > <https://opensource.org/licenses/MS-RL> > > Do you know if WiX runs in Mono? That would allow us to produce > installers directly from openvpn-build without having to have a separate > Windows packaging computer in the build chain. >
Any reason why you specifically want to use WiX? Are msibuild or wixl (from msitools[0]) not good enough? I know those lack features, but if they're good enough I would prefer using something that is packaged by many distros (and doesn't need mono). -Steffan [0] https://wiki.gnome.org/msitools ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
