>> It would need to be twice the size (two copies of everything), > > Size matters not :) > >> but besides that it would be really convenient indeed. >> >> *Building* that would require major work in the build system (which >> today gets told "build for *this* architecture and come up with a >> final installer!" and is sufficiently... $insertpoliteword that is not >> easy to extend. >> >> But then, it's not mine anyway, maybe Samuli likes this idea so much... :-) > > Unlikely :)
Indeed :). I'm not really volunteering for this, but making a wrapper installer that has both 32-bit and 64-bit installers is probably quite doable without touching openvpn-build at all / very little. The wrapper installer would just launch the appropriate installer depending on the bitness of the operating system. As we already have experience about installers within installers, this would just add one more layer. As long as the installer does not become recursive we should be fine :). I'm open to publishing wrapper installers, especially if somebody else writes the NSIS code :). -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock ------------------------------------------------------------------------------ _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
