Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

> 2012/2/20 Samuli Seppänen >>> Here are the tasks to perform: >>> 1. Create a GIT repository of the master TAP-Win32 sources with all >>> history, to ease our work, please use github. >> Any thoughts of this anyone? Personally, I don't care where the source >> code lives. It seems[1] that GitHub

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

2012/2/20 Samuli Seppänen > > Here are the tasks to perform: > > 1. Create a GIT repository of the master TAP-Win32 sources with all > > history, to ease our work, please use github. > Any thoughts of this anyone? Personally, I don't care where the source > code lives. It seems[1] that GitHub can

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

Hi Alon, > Hello, > > We have a go to rewrite the OpenvPN build system. > I started to work at core product [1]. > > As part of the re-write we split out the TAP-Win32 out of OpenVPN code base. > > To make things go faster we may try to parallelize the effort. > > Here are the tasks to perform: > 1

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

>> > >> > 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/gma

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

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.

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

-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" > wrote: >> 9. Output of build system would be [at least] (msi, tarball) for >> (win32, win64). Why tarball? To enable people to fetch fil

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18/02/12 16:05, Alon Bar-Lev wrote: > Hello, > > We have a go to rewrite the OpenvPN build system. I started to work at > core product [1]. > > As part of the re-write we split out the TAP-Win32 out of OpenVPN code > base. > > To make things go f

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

On 02/18/2012 04:53:50 PM, Scott Zeid wrote: > On Feb 18, 2012 9:05 AM, "Alon Bar-Lev" > 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 sh

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

On Feb 18, 2012 9:05 AM, "Alon Bar-Lev" 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 tarba

Re: [Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

On 02/18/2012 09:05:16 AM, Alon Bar-Lev wrote: > Hello, > > We have a go to rewrite the OpenvPN build system. > 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). I'd

[Openvpn-devel] [DEVELOPER REQUESTED] Repackage TAP-Win32

Hello, We have a go to rewrite the OpenvPN build system. I started to work at core product [1]. As part of the re-write we split out the TAP-Win32 out of OpenVPN code base. To make things go faster we may try to parallelize the effort. Here are the tasks to perform: 1. Create a GIT repository o