> On Fri, Feb 24, 2012 at 9:33 AM, Adriaan de Jong <dej...@fox-it.com> wrote: >>> I did not add the UI stuff, I think there should be a discussion why >>> these are embedded. >>> >> One of the few pieces criticism we got about the OpenVPN-NL release was the >> fact that we didn't bundle the GUI. End-users expect an all-in-one installer >> for a simple user experience. As an end user of OpenVPN, I agree. On >> Windows, I don't want to use the command line, as it is very painful. > There are two options which are better. > > 1. Embed openvpn installer within the UI of your choice. > > 2. Embed more defined UI installer into openvpn installer. > > In both cases every project handles the installation of its own components. > Makes sense, especially when as we're splitting the TAP-driver, easy-rsa, etc. into separate subprojects. I would prefer 2) where each subproject would have it's own installer, which the OpenVPN "bundle" installer could call as necessary. As a bonus, each subproject could be installed separately without touching OpenVPN itself. The only downside would be some duplicate code in the installer scripts.
-- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
