openvpn-devel Mailing List for OpenVPN

On 02/18/2012 06:04:48 PM, David Sommerseth wrote: > Right now, debating tarball/zipball formats is a bit premature. > There > are 8 challenging steps to solve before this. Even though Windows > doesn't support tarballs natively, LGPL tools like 7-Zip exists which > will make that job easier. And those needing to extract these pieces > are > not necessarily end-users, so we should expect people to know how to > solve these things. > > But for now, I'd like to see more focus on the steps before the > packaging > method. We first need to have something to package. Makes sense. Regardless... You might try my old patch that produces a tarball of MS binaries, found here: http://article.gmane.org/gmane.network.openvpn.devel/2578 It never got applied, partly because it needed supporting documentation and the accompanying patch to update the website failed to apply by the time anybody got around to looking at the patch. because by then the website was reorganized. Even if it does apply, it should have supporting documentation before being accepted into the tree. I can't say if it's easier to poke about the old thread to come up with appropriate documentation or to start from scratch. Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein 

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/02/12 23:53, Scott Zeid wrote: > > On Feb 18, 2012 9:05 AM, "Alon Bar-Lev" <alo...@gm... > <mailto:alo...@gm...>> wrote: >> 9. Output of build system would be [at least] (msi, tarball) for >> (win32, win64). Why tarball? To enable people to fetch files >> without hacking the msi (example: cross compile). > > It should probably be a zip file since Windows doesn't support > tarballs out of the box. Right now, debating tarball/zipball formats is a bit premature. There are 8 challenging steps to solve before this. Even though Windows doesn't support tarballs natively, LGPL tools like 7-Zip exists which will make that job easier. And those needing to extract these pieces are not necessarily end-users, so we should expect people to know how to solve these things. But for now, I'd like to see more focus on the steps before the packaging method. We first need to have something to package. kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9APJ4ACgkQDC186MBRfrpdvgCgleyQ6VldHLmpj0FR/TO5RQ8l CSAAnAmbJCFoCgon5QOFcfAupTZdOMZY =9nxF -----END PGP SIGNATURE-----