References: <99D61A626FDA8A4B90A270669121BE108587171C@...2294...> <99D61A626FDA8A4B90A270669121BE1085875356@...2294...> <99D61A626FDA8A4B90A270669121BE1085876852@...2294...> <023dbb4e-47b6-bceb-8913-40d5bf4ae76e@...515...> <99D61A626FDA8A4B90A270669121BE1085877307@...2294...> <031e4c73-3317-585d-38af-30ac9fede8ff@...515...> From: =?UTF-8?Q?Samuli_Sepp=c3=a4nen?= Message-ID: <9392cea0-2b29-b7e1-221c-1f9daecd2add@...515...> Date: Thu, 2 Nov 2017 10:51:12 +0200 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Subject: Re: [Openvpn-devel] OpenVPN Interactive Service Branding List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable To: Steffan Karger , openvpn-devel@lists.sourceforge.net On 02/11/2017 10:41, Steffan Karger wrote: > Hi, >=20 > On 02-11-17 09:31, Samuli Sepp=C3=A4nen 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 mome= nt four >>>> (other) people who have expressed interest in taking part in the "crea= te 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 bui= lds 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: >> >> >> >> It seems that WiX which you mention would probably be our tool of >> choice, given it is open source (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. >> >=20 > 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). >=20 Ah, excellent find! I'm definitely not opposed to msitools if it fits the bill. Samuli