-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27/02/12 09:57, Samuli Seppänen wrote: > >> 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.
If each sub-project just bundles .msi installers, that would just be smooth! Where a "global" installer bundles it into a single package for OpenVPN. Which means other projects which needs a TAP driver on Windows can just pull down our MSI installer and bundle that one. Upgrades could also be handled much smoother than now. The "global" installer detects if the sub-components are up-to-date or not, and updates just the needed packages. kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9LVCoACgkQDC186MBRfroAJACfZ0GB+2wiHKk9FJlgVxbbsyo0 fTsAn3YwKBltC35+UBeb0i8kbPSKIq8z =I3lE -----END PGP SIGNATURE-----
