Re: [Openvpn-devel] openvpn windows gui

[Samuli Seppänen]

Il 28.02.2012 14:55, Jan Just Keijser ha scritto:
> Samuli Seppänen wrote:
 We should probably write an installer.
   
>>> I'm not sure if it's the best idea to make each and every GUI project out 
>>> there write it's own installer, when it's mostly a single executable that 
>>> needs to be replaced to package it with upstream openvpn. The pragmatic way 
>>> to 
>>> do it would be to leave the GUI stuff in openvpn itself, but I guess you 
>>> guys 
>>> like the idea of bundling installers with other installers, right?
>>>
>>> Heiko 
>>> 
>> Right :). The primary benefit I see in having separate installers for
>> the OpenVPN-GUI, TAP-driver and easy-rsa is the possibility of
>> installing and upgrading each component separately more easily. It might
>> even be possible (=have not checked) to have the "OpenVPN Windows
>> installer bundle" fetch the latest dependency installers from predefined
>> URLs prior to installation and fallback to included ones if that fails.
>> Not sure if we want do that, but it's an option.
>>
>>   
> e, it would be nice to keep/have a "single click install" option - 
> one of the nice features of the current OpenVPN installer is that you 
> get everything in one download. Also, it will ensure that there is at 
> least one set of components that works together.
>
> JM2CW,
>
> JJK
Agreed. I think having all the dependencies in one installer is
necessary, so that Internet access is not required during install. The
"fetch updated dependencies from the Internet" would be most useful for
things like important bugfixes and security updates, which shouldn't in
general create compatibility headaches.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

Re: [Openvpn-devel] openvpn windows gui

[Alon Bar-Lev]

2012/2/28 Jan Just Keijser :
> Samuli Seppänen wrote:

 We should probably write an installer.

>>>
>>> I'm not sure if it's the best idea to make each and every GUI project out
>>> there write it's own installer, when it's mostly a single executable that
>>> needs to be replaced to package it with upstream openvpn. The pragmatic way
>>> to do it would be to leave the GUI stuff in openvpn itself, but I guess you
>>> guys like the idea of bundling installers with other installers, right?
>>>
>>> Heiko
>>
>>
>> Right :). The primary benefit I see in having separate installers for
>> the OpenVPN-GUI, TAP-driver and easy-rsa is the possibility of
>> installing and upgrading each component separately more easily. It might
>> even be possible (=have not checked) to have the "OpenVPN Windows
>> installer bundle" fetch the latest dependency installers from predefined
>> URLs prior to installation and fallback to included ones if that fails.
>> Not sure if we want do that, but it's an option.
>>
>>
>
> e, it would be nice to keep/have a "single click install" option - one
> of the nice features of the current OpenVPN installer is that you get
> everything in one download. Also, it will ensure that there is at least one
> set of components that works together.
>
> JM2CW,
>
> JJK
>
>

The new Installer installs easy-rsa and openvpn-gui.
Soon also the tap.

Alon.

Re: [Openvpn-devel] openvpn windows gui

[Jan Just Keijser]

Samuli Seppänen wrote:

We should probably write an installer.
  
I'm not sure if it's the best idea to make each and every GUI project out 
there write it's own installer, when it's mostly a single executable that 
needs to be replaced to package it with upstream openvpn. The pragmatic way to 
do it would be to leave the GUI stuff in openvpn itself, but I guess you guys 
like the idea of bundling installers with other installers, right?


Heiko 



Right :). The primary benefit I see in having separate installers for
the OpenVPN-GUI, TAP-driver and easy-rsa is the possibility of
installing and upgrading each component separately more easily. It might
even be possible (=have not checked) to have the "OpenVPN Windows
installer bundle" fetch the latest dependency installers from predefined
URLs prior to installation and fallback to included ones if that fails.
Not sure if we want do that, but it's an option.

  
e, it would be nice to keep/have a "single click install" option - 
one of the nice features of the current OpenVPN installer is that you 
get everything in one download. Also, it will ensure that there is at 
least one set of components that works together.


JM2CW,

JJK

Re: [Openvpn-devel] openvpn windows gui

[Alon Bar-Lev]

On Mon, Feb 27, 2012 at 6:18 PM, Alon Bar-Lev  wrote:
> Will be ready in a few hours.

Done [1].
Tarball is available.
Please review/pull.

Basically you need to modify the --with-crypto...
With:
./configure CFLAGS="-Ixxx/include" LDFLAGS="-Lxxx/lib"
Where xxx is the openssl location.
The build script now also builds the gui, so you use it...

I added --enable-deponly to allow "make dist" at Linux.

[1] https://github.com/alonbl/openvpn-gui
[2] https://github.com/alonbl/openvpn-build

Re: [Openvpn-devel] openvpn windows gui

[Alon Bar-Lev]

On Mon, Feb 27, 2012 at 6:04 PM, Heiko Hund  wrote:
> Hi Alon
>
> On Monday 27 February 2012 14:01:25 Alon Bar-Lev wrote:
>> I am going to re-write your build system :)
>
> Take it easy! =)
>
>> It uses autoconf but not automake and looks some rewrite is needed.
>
> I did not see the the need for automake in the past. However, now that dist
> produces a .tar.gz and there's the res/ subdir and the Makefile is quite ugly,
> plus not all the dependency tracking is in place working, a little automake
> will be beneficial, so go ahead. Please make sure the snapshot target stays
> intact and that configure still supports the --with-cyrpto-* arguments for
> libcrypto (guess you'll go pkg-config here as well).

Great.
The crypto stuff will be converted to pkg-config style OPENSSL_CFLAGS
and OPENSSL_LIBS.
The automake move will make the build much easier to maintain.

>> We should probably write an installer.
>
> I'm not sure if it's the best idea to make each and every GUI project out
> there write it's own installer, when it's mostly a single executable that
> needs to be replaced to package it with upstream openvpn. The pragmatic way to
> do it would be to leave the GUI stuff in openvpn itself, but I guess you guys
> like the idea of bundling installers with other installers, right?

If this is a single .exe I will put this in installer for now as-is.

Will be ready in a few hours.

Alon.

Re: [Openvpn-devel] openvpn windows gui

[Heiko Hund]

Hi Alon

On Monday 27 February 2012 14:01:25 Alon Bar-Lev wrote:
> I am going to re-write your build system :)

Take it easy! =)

> It uses autoconf but not automake and looks some rewrite is needed.

I did not see the the need for automake in the past. However, now that dist 
produces a .tar.gz and there's the res/ subdir and the Makefile is quite ugly, 
plus not all the dependency tracking is in place working, a little automake 
will be beneficial, so go ahead. Please make sure the snapshot target stays 
intact and that configure still supports the --with-cyrpto-* arguments for 
libcrypto (guess you'll go pkg-config here as well).

> We should probably write an installer.

I'm not sure if it's the best idea to make each and every GUI project out 
there write it's own installer, when it's mostly a single executable that 
needs to be replaced to package it with upstream openvpn. The pragmatic way to 
do it would be to leave the GUI stuff in openvpn itself, but I guess you guys 
like the idea of bundling installers with other installers, right?

Heiko 
-- 
Heiko Hund | Software Engineer | Phone +49-721-25516-237 | Fax -200
Astaro a Sophos Company | Amalienbadstr. 41 Bau 52 | 76227 Karlsruhe | Germany
Commercial Register: Mannheim HRA 702710 | Headquarter Location: Karlsruhe
 
Represented by the General Partner Astaro Verwaltungs GmbH
Amalienbadstraße 41 Bau 52 | 76227 Karlsruhe | Germany 
Commercial Register: Mannheim HRB 708248 | Executive Board: Gert Hansen,
Markus Hennig, Jan Hichert, Günter Junk, Dr. Frank Nellissen

Re: [Openvpn-devel] openvpn windows gui

[Alon Bar-Lev]

2012/2/27 Samuli Seppänen :
>
>> Hello,
>>
>> A stupid question
>> Which GUI is embedded in the installer?
>> What is GUI and what is XGUI?
>> All I found is[1].
>>
> In 2.2.x installers the GUI is the old one from here, just signed:
>
> 
>
> In 2.3-alpha1 we use the latest snapshot from here:
>
> 
>
> XGUI is obsolete, it can be ignored. I removed all of the XGUI-related
> stuff from the Python-based buildsystem, but it's still lurking in the
> old "domake-win" buildscripts/.nsi files.
>

Hello Heiko,

I am going to re-write your build system :)
It uses autoconf but not automake and looks some rewrite is needed.
We should probably write an installer.

Is that OK?

Alon.

Re: [Openvpn-devel] openvpn windows gui

[Samuli Seppänen]

> Hello,
>
> A stupid question
> Which GUI is embedded in the installer?
> What is GUI and what is XGUI?
> All I found is[1].
>
In 2.2.x installers the GUI is the old one from here, just signed:



In 2.3-alpha1 we use the latest snapshot from here:



XGUI is obsolete, it can be ignored. I removed all of the XGUI-related
stuff from the Python-based buildsystem, but it's still lurking in the
old "domake-win" buildscripts/.nsi files.

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

[Openvpn-devel] openvpn windows gui

[Alon Bar-Lev]

Hello,

A stupid question
Which GUI is embedded in the installer?
What is GUI and what is XGUI?
All I found is[1].

Alon.

[1] 
http://openvpn-gui.git.sourceforge.net/git/gitweb.cgi?p=openvpn-gui/openvpn-gui;a=summary