* [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1
@ 2010-04-25 23:47 Toby Thain
2010-04-26 8:42 ` Arnoud Vermeer
2010-04-26 11:34 ` [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1 David Sommerseth
0 siblings, 2 replies; 24+ messages in thread
From: Toby Thain @ 2010-04-25 23:47 UTC (permalink / raw)
To: openvpn-users; +Cc: openvpn-devel
Hi,
I have put together a generic packaging script for OS X (pkg/dmg), and
created basic binary Installer packages for PowerPC and Intel. It's
meant only for distributing the generic binary distribution, analogous
to any other UNIX binary package. A small addition is a script which
installs an OS X launchd service, net.openvpn.
The binary package can be combined with a separate per-client key pkg
that installs configuration and keys and starts the launchd service
(scripts also available for this, in key-package directory).
This may help people with simple deployments that include OS X
clients. I have not linked to built packages, on the theory that
there's little reason you should trust my builds. (If you have the
Apple Developer Tools, and archives for openvpn and lzo, then creating
the binary packages and disk image yourself, for whatever architecture
you run, is as simple as 'make dmg'. Package build, install and run
have been tested on 32-bit PowerPC and Intel.)
cc'd devel list in case there is any interest in adopting the
packaging script(s), perhaps as contrib?
http://telegraphics.com.au/svn/openvpn-package/trunk/
--Toby
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1
2010-04-25 23:47 [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1 Toby Thain
@ 2010-04-26 8:42 ` Arnoud Vermeer
2010-04-26 14:47 ` Karl O. Pinc
2010-04-26 11:34 ` [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1 David Sommerseth
1 sibling, 1 reply; 24+ messages in thread
From: Arnoud Vermeer @ 2010-04-26 8:42 UTC (permalink / raw)
To: Toby Thain <toby@; +Cc: openvpn-devel, openvpn-users
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
Hi Toby,
I for one appreciate your effort and would love to see this in the standard
release process.
Kind regards,
Arnoud Vermeer
On Mon, Apr 26, 2010 at 1:47 AM, Toby Thain <toby@...1348...>wrote:
> Hi,
>
> I have put together a generic packaging script for OS X (pkg/dmg), and
> created basic binary Installer packages for PowerPC and Intel. It's
> meant only for distributing the generic binary distribution, analogous
> to any other UNIX binary package. A small addition is a script which
> installs an OS X launchd service, net.openvpn.
>
> The binary package can be combined with a separate per-client key pkg
> that installs configuration and keys and starts the launchd service
> (scripts also available for this, in key-package directory).
>
> This may help people with simple deployments that include OS X
> clients. I have not linked to built packages, on the theory that
> there's little reason you should trust my builds. (If you have the
> Apple Developer Tools, and archives for openvpn and lzo, then creating
> the binary packages and disk image yourself, for whatever architecture
> you run, is as simple as 'make dmg'. Package build, install and run
> have been tested on 32-bit PowerPC and Intel.)
>
> cc'd devel list in case there is any interest in adopting the
> packaging script(s), perhaps as contrib?
>
> http://telegraphics.com.au/svn/openvpn-package/trunk/
>
> --Toby
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>
[-- Attachment #2: Type: text/html, Size: 2329 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1
2010-04-25 23:47 [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1 Toby Thain
2010-04-26 8:42 ` Arnoud Vermeer
@ 2010-04-26 11:34 ` David Sommerseth
2010-04-26 12:08 ` Toby Thain
1 sibling, 1 reply; 24+ messages in thread
From: David Sommerseth @ 2010-04-26 11:34 UTC (permalink / raw)
To: Toby Thain <toby@; +Cc: openvpn-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 26/04/10 01:47, Toby Thain wrote:
> Hi,
>
> I have put together a generic packaging script for OS X (pkg/dmg), and
> created basic binary Installer packages for PowerPC and Intel. It's
> meant only for distributing the generic binary distribution, analogous
> to any other UNIX binary package. A small addition is a script which
> installs an OS X launchd service, net.openvpn.
>
> The binary package can be combined with a separate per-client key pkg
> that installs configuration and keys and starts the launchd service
> (scripts also available for this, in key-package directory).
>
> This may help people with simple deployments that include OS X
> clients. I have not linked to built packages, on the theory that
> there's little reason you should trust my builds. (If you have the
> Apple Developer Tools, and archives for openvpn and lzo, then creating
> the binary packages and disk image yourself, for whatever architecture
> you run, is as simple as 'make dmg'. Package build, install and run
> have been tested on 32-bit PowerPC and Intel.)
>
> cc'd devel list in case there is any interest in adopting the
> packaging script(s), perhaps as contrib?
>
> http://telegraphics.com.au/svn/openvpn-package/trunk/
Even though I don't have a OSX box (nor I do I have any plans acquiring
any), this looks pretty nice and cool!
Would it be any possibilities that you would be willing to try to twist
this into the openvpn-testing.git tree? It would sure fit well into the
contrib/ collection.
Maybe even do some research if it would be possible, appropriate and
good to try to make autotools do a lot of this work automatically if
requested? I'm not sure if this really is appropriate, but let's
consider it at least.
Or that when running ./configure on an identified OSX box, that it would
update the contrib/ Makefile so a user can just go into the contrib/
directory and run make to get a proper OSX package.
/me is just thinking out aloud :)
kind regards,
David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkvVelQACgkQDC186MBRfrpB3gCdEmal8SRyLhf/ZrK5Ub495zC+
k3oAoK1FcTi43h57qjqLCv5kpvdGVQtF
=FJ38
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1
2010-04-26 11:34 ` [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1 David Sommerseth
@ 2010-04-26 12:08 ` Toby Thain
2010-04-26 12:47 ` David Sommerseth
0 siblings, 1 reply; 24+ messages in thread
From: Toby Thain @ 2010-04-26 12:08 UTC (permalink / raw)
To: David Sommerseth <openvpn.list@; +Cc: openvpn-devel
On 26-Apr-10, at 9:34 PM, David Sommerseth wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 26/04/10 01:47, Toby Thain wrote:
>> Hi,
>>
>> I have put together a generic packaging script for OS X (pkg/dmg),
>> and
>> created basic binary Installer packages for PowerPC and Intel. It's
>> meant only for distributing the generic binary distribution,
>> analogous
>> to any other UNIX binary package. A small addition is a script which
>> installs an OS X launchd service, net.openvpn.
>>
>> The binary package can be combined with a separate per-client key pkg
>> that installs configuration and keys and starts the launchd service
>> (scripts also available for this, in key-package directory).
>>
>> This may help people with simple deployments that include OS X
>> clients. I have not linked to built packages, on the theory that
>> there's little reason you should trust my builds. (If you have the
>> Apple Developer Tools, and archives for openvpn and lzo, then
>> creating
>> the binary packages and disk image yourself, for whatever
>> architecture
>> you run, is as simple as 'make dmg'. Package build, install and run
>> have been tested on 32-bit PowerPC and Intel.)
>>
>> cc'd devel list in case there is any interest in adopting the
>> packaging script(s), perhaps as contrib?
>>
>> http://telegraphics.com.au/svn/openvpn-package/trunk/
>
> Even though I don't have a OSX box (nor I do I have any plans
> acquiring
> any), this looks pretty nice and cool!
>
> Would it be any possibilities that you would be willing to try to
> twist
> this into the openvpn-testing.git tree? It would sure fit well into
> the
> contrib/ collection.
>
> Maybe even do some research if it would be possible, appropriate and
> good to try to make autotools do a lot of this work automatically if
> requested? I'm not sure if this really is appropriate, but let's
> consider it at least.
>
> Or that when running ./configure on an identified OSX box, that it
> would
> update the contrib/ Makefile so a user can just go into the contrib/
> directory and run make to get a proper OSX package.
This latter is pretty much what I had in mind, for adapting to
contrib. I think it will be easier than the autotools route (and my
time for this is limited - from experience futzing with autotools can
soak up a *lot* of time...) That said, I'd prefer to do it the *right*
way, so I won't dismiss that route.
I am a git novice, so I don't think it will be ready for inclusion
soon, but thankyou for the encouraging feedback, David. When I find
some time I'll see if I can check out the testing branch and prepare a
patch.
--Toby
>
> /me is just thinking out aloud :)
>
>
> kind regards,
>
> David Sommerseth
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkvVelQACgkQDC186MBRfrpB3gCdEmal8SRyLhf/ZrK5Ub495zC+
> k3oAoK1FcTi43h57qjqLCv5kpvdGVQtF
> =FJ38
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1
2010-04-26 12:08 ` Toby Thain
@ 2010-04-26 12:47 ` David Sommerseth
0 siblings, 0 replies; 24+ messages in thread
From: David Sommerseth @ 2010-04-26 12:47 UTC (permalink / raw)
To: Toby Thain <toby@; +Cc: openvpn-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 26/04/10 14:08, Toby Thain wrote:
[...snip...]
>>> cc'd devel list in case there is any interest in adopting the
>>> packaging script(s), perhaps as contrib?
>>>
>>> http://telegraphics.com.au/svn/openvpn-package/trunk/
>>
>> Even though I don't have a OSX box (nor I do I have any plans acquiring
>> any), this looks pretty nice and cool!
>>
>> Would it be any possibilities that you would be willing to try to twist
>> this into the openvpn-testing.git tree? It would sure fit well into the
>> contrib/ collection.
>>
>> Maybe even do some research if it would be possible, appropriate and
>> good to try to make autotools do a lot of this work automatically if
>> requested? I'm not sure if this really is appropriate, but let's
>> consider it at least.
>>
>> Or that when running ./configure on an identified OSX box, that it would
>> update the contrib/ Makefile so a user can just go into the contrib/
>> directory and run make to get a proper OSX package.
>
> This latter is pretty much what I had in mind, for adapting to contrib.
> I think it will be easier than the autotools route (and my time for this
> is limited - from experience futzing with autotools can soak up a *lot*
> of time...) That said, I'd prefer to do it the *right* way, so I won't
> dismiss that route.
Sure, no stress! Take the time you need, and you may start easier and
modify it later on as well!
> I am a git novice, so I don't think it will be ready for inclusion soon,
> but thankyou for the encouraging feedback, David. When I find some time
> I'll see if I can check out the testing branch and prepare a patch.
Fair enough! I've put together a very quick "git crash course", which
might help you getting acquainted and started with git.
<http://www.secure-computing.net/wiki/index.php/OpenVPN/git_crash_course>
Also see the developers docs for more resources:
<http://www.secure-computing.net/wiki/index.php/OpenVPN/Developer_documentation>
I can especially recommend the ProGit Book (there is a link on the
Developer docs page) It's a good starting point when you want to learn
and/or understand more about git and its features.
kind regards,
David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkvVi2gACgkQDC186MBRfrrB8gCfayAZB1a2Qx3Qb6EVvLDSWggI
2DMAmwbYjPfYZvM+aVNTOUvW0fbs1HVN
=ZsNw
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1
2010-04-26 8:42 ` Arnoud Vermeer
@ 2010-04-26 14:47 ` Karl O. Pinc
2010-04-26 15:23 ` [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1) David Sommerseth
0 siblings, 1 reply; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-26 14:47 UTC (permalink / raw)
To: Arnoud Vermeer <a.vermeer@; +Cc: Toby Thain <toby@
On 04/26/2010 03:42:37 AM, Arnoud Vermeer wrote:
> Hi Toby,
>
> I for one appreciate your effort and would love to see this in the
> standard
> release process.
Speaking of the standard release process there is still this thread:
Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building
2.1 rc15 on Windows XP
and its patch for releasing unpackaged MS Windows binaries;
quite similar to what you're proposing for OS/X. There has been
no response from this list regarding this for quite some
time despite repeated requests, unless I missed something
somewhere along the line.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 14:47 ` Karl O. Pinc
@ 2010-04-26 15:23 ` David Sommerseth
2010-04-26 15:58 ` Karl O. Pinc
2010-04-29 3:04 ` Karl O. Pinc
0 siblings, 2 replies; 24+ messages in thread
From: David Sommerseth @ 2010-04-26 15:23 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, openvpn-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 26/04/10 16:47, Karl O. Pinc wrote:
> On 04/26/2010 03:42:37 AM, Arnoud Vermeer wrote:
>> Hi Toby,
>>
>> I for one appreciate your effort and would love to see this in the
>> standard
>> release process.
>
> Speaking of the standard release process there is still this thread:
>
> Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building
> 2.1 rc15 on Windows XP
>
> and its patch for releasing unpackaged MS Windows binaries;
> quite similar to what you're proposing for OS/X. There has been
> no response from this list regarding this for quite some
> time despite repeated requests, unless I missed something
> somewhere along the line.
Hi Karl,
Thanks for pushing this. I am honestly not quite sure were we stand
with that patch. And since I understand the Windows building least of
all, I've refrained from going into details of this one so far. It has
not been my intention of ignoring this patch. I'm primarily focusing on
the platforms I happen to understand better, and hope others will chime
in on the other issues.
But as responses are missing, I'll try to find some time in the near
future (this week is crazily hectic for me) - to see if I can understand
what your patch solves. That is a little bit unclear to me, as the
patch I'm looking at seems to just make a tarball with compiled binaries
... Right now, I do not immediately see what problem that solves. But
I'm pretty sure I'm overlooking something!
Btw, you mentioned in some of the threads that you would look at some of
the docs for this as well. I remember vaguely something about another
set of patches for HTML files - which I can't say I've seen in the
source tree. That would be good to get into the tree together with this
patch when I've looked at it a bit better.
kind regards,
David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkvVr+kACgkQDC186MBRfrrCZQCdF46SLpVlvXIIxZ/j+Jyl/JuS
CegAni6GRYW/nSN6AuNmJK7Y0/CYqnBY
=HOVE
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 15:23 ` [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1) David Sommerseth
@ 2010-04-26 15:58 ` Karl O. Pinc
2010-04-26 16:53 ` Peter Stuge
2010-04-26 23:19 ` Toby Thain
2010-04-29 3:04 ` Karl O. Pinc
1 sibling, 2 replies; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-26 15:58 UTC (permalink / raw)
To: David Sommerseth <openvpn.list@; +Cc: openvpn-devel, openvpn-users
On 04/26/2010 10:23:21 AM, David Sommerseth wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 26/04/10 16:47, Karl O. Pinc wrote:
> > Speaking of the standard release process there is still this
> thread:
> >
> > Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems
> building
>
> > 2.1 rc15 on Windows XP
> >
> > and its patch for releasing unpackaged MS Windows binaries;
> > quite similar to what you're proposing for OS/X.
> Thanks for pushing this. I am honestly not quite sure were we stand
> with that patch. And since I understand the Windows building least
> of
> all, I've refrained from going into details of this one so far. It
> has
> not been my intention of ignoring this patch. I'm primarily focusing
> on
> the platforms I happen to understand better, and hope others will
> chime
> in on the other issues.
>
> But as responses are missing, I'll try to find some time in the near
> future (this week is crazily hectic for me) - to see if I can
> understand
> what your patch solves. That is a little bit unclear to me, as the
> patch I'm looking at seems to just make a tarball with compiled
> binaries
> ... Right now, I do not immediately see what problem that solves.
> But
> I'm pretty sure I'm overlooking something!
>
> Btw, you mentioned in some of the threads that you would look at some
> of
> the docs for this as well. I remember vaguely something about
> another
> set of patches for HTML files - which I can't say I've seen in the
> source tree. That would be good to get into the tree together with
> this
> patch when I've looked at it a bit better.
It's a packaging policy issue.
The problem addressed is that there only binaries available
for MS Windows are pre-packaged in an installer executable.
This means that anyone who wants stock binaries but a
modified installer has to recompile from source.
There are many reasons why one would want a non-stock
MS Windows installer -- the foremost being to include
an OpenVPN configuration file that allows connections
between pre-designated endpoints. One might want to
go so far as to include certificates in the installation
to secure the communications channel. ;-)
Creating custom installation executables is
relatively easy, especially as the OpenVPN code base
includes a working config file that's used to make
the installer OpenVPN distributes. But of course
OpenVPN binaries are a requirement before packaging
can be attempted.
Recompiling is both complicated and error prone. Historically
there are a number of issues that make compiling difficult.
I recall problems with mingw versions
when compiling on MS Windows and some other sort of problems
when trying to cross compile from Linux. In any case it's
clear that compiling will always be relatively complicated
and time-consuming to setup in comparison with downloading
binaries.
So, there are 2 patches. The first is to the OpenVPN
build process. It produces unpackaged MS Windows binaries
and (last you wrote) it works. The second patch is to
the OpenVPN documentation. It documents that the
binaries exist and when you want them. It does not
apply because the OpenVPN website has since been
restructured. The doc patch needs to be re-worked
to put the text in the appropriate place.
But this only makes sense if OpenVPN _will_ release
unpackaged MS Windows binaries. It makes sense to me;
the project is already releasing unpackaged Linux
binaries and it now talking about doing the same
for OS/X binaries. There's clear utility. Regardless,
this is a policy decision. Getting a resolution on
packaging policy seems to me to be the first step.
If OpenVPN _won't'_ release unpackaged MS Windows
binaries I'd like to know why so it would be
nice if whomever moves this forward, as with
any other patch, solicits more than a yes/no answer.
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 15:58 ` Karl O. Pinc
@ 2010-04-26 16:53 ` Peter Stuge
2010-04-26 19:11 ` Karl O. Pinc
2010-04-26 23:19 ` Toby Thain
1 sibling, 1 reply; 24+ messages in thread
From: Peter Stuge @ 2010-04-26 16:53 UTC (permalink / raw)
To: openvpn-devel
Karl O. Pinc wrote:
> the project is already releasing unpackaged Linux
> binaries
Really?
> and it now talking about doing the same for OS/X binaries.
Recently discussed work for contrib/ produces a .dmg, very much a
package in my view.
> There's clear utility.
I guess it depends. I'm not sure that I agree that compilation is a
much bigger bother than (cross-)compiling the NSIS installer..
But, I do agree with you that there is utility.
//Peter
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 16:53 ` Peter Stuge
@ 2010-04-26 19:11 ` Karl O. Pinc
2010-04-26 23:02 ` David Sommerseth
` (2 more replies)
0 siblings, 3 replies; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-26 19:11 UTC (permalink / raw)
To: Peter Stuge <peter@; +Cc: openvpn-devel
On 04/26/2010 11:53:19 AM, Peter Stuge wrote:
> Karl O. Pinc wrote:
> > the project is already releasing unpackaged Linux
> > binaries
>
> Really?
They seem to have stopped sometime after July 30 2008.
http://web.archive.org/web/20080730205524/openvpn.net/index.php/
downloads.html
It's hard to tell when because archive.org does not appear
to be allowed to archive the site any longer. Or at least
there's nothing more recent. (This seems silly. I wonder why.)
(I clearly haven't been downloading binaries in a while.
Probably because I rely on my distro for binaries so
they can do the systems integration and security patches,
or I am getting development from CVS/git.
IMO people who don't rely on their distro for systems integration
and security patches are asking for trouble. There are of course
always reasons to make specific exceptions, RH comes to mind. :)
Is OpenVPN in RHEL6?)
>
> > and it now talking about doing the same for OS/X binaries.
>
> Recently discussed work for contrib/ produces a .dmg, very much a
> package in my view.
Ok. I don't know much about .dmg. I thought they were basically
tarballs by another name in that they just stick stuff somewhere.
My Mac usage is sporadic, sorry.
>
>
> > There's clear utility.
>
> I guess it depends. I'm not sure that I agree that compilation is a
> much bigger bother than (cross-)compiling the NSIS installer..
On Debian all I had to do was "aptitude install nsis" and then
run it to make MS Windows installers. Plug and play, no
compiling necessary.
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 19:11 ` Karl O. Pinc
@ 2010-04-26 23:02 ` David Sommerseth
2010-04-27 2:25 ` Karl O. Pinc
2010-04-26 23:31 ` Toby Thain
2010-04-27 4:04 ` Karl O. Pinc
2 siblings, 1 reply; 24+ messages in thread
From: David Sommerseth @ 2010-04-26 23:02 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, Peter Stuge <peter@
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 26/04/10 21:11, Karl O. Pinc wrote:
> On 04/26/2010 11:53:19 AM, Peter Stuge wrote:
>> Karl O. Pinc wrote:
[...snip...]
> IMO people who don't rely on their distro for systems integration
> and security patches are asking for trouble. There are of course
> always reasons to make specific exceptions, RH comes to mind. :)
>
> Is OpenVPN in RHEL6?)
Yes, I'm pretty sure it is. RHEL5 even shipped OpenVPN 2.1_rc15 for a
long time as a stable release until OpenVPN released 2.1.1. In
RHEL5.4/CentOS5.4, I'm pretty sure 2.1.1 is standard by now.
Those releases are also pretty much in sync with the upstream OpenVPN
release. No extra security fixes which is not in OpenVPN - as it should
be, IMHO. From what I've seen in the Fedora builds, it's mostly
distro-specific adjustments added on top of the OpenVPN 2.1.1 tarball.
But I agree that using a distro-based installation, gives you the
upgrades in a very convenient way. Automatically - and you get a
reminder regularly.
>>> and it now talking about doing the same for OS/X binaries.
>>
>> Recently discussed work for contrib/ produces a .dmg, very much a
>> package in my view.
>
> Ok. I don't know much about .dmg. I thought they were basically
> tarballs by another name in that they just stick stuff somewhere.
> My Mac usage is sporadic, sorry.
>
>>
>>> There's clear utility.
>>
>> I guess it depends. I'm not sure that I agree that compilation is a
>> much bigger bother than (cross-)compiling the NSIS installer..
>
> On Debian all I had to do was "aptitude install nsis" and then
> run it to make MS Windows installers. Plug and play, no
> compiling necessary.
>
Just a little nitpick, when you run makensis, that's actually
compilation of the installer - even when you're doing it on Linux. You
get a Windows binary as the result.
kind regards,
David Sommerseth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkvWG5YACgkQDC186MBRfro2bQCfX3H740h3QErt8+fzPlwVNekk
btIAn3RMwwuLQCfrrfe29SSW46nZP9Tp
=XOWD
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 15:58 ` Karl O. Pinc
2010-04-26 16:53 ` Peter Stuge
@ 2010-04-26 23:19 ` Toby Thain
2010-04-27 2:19 ` Karl O. Pinc
1 sibling, 1 reply; 24+ messages in thread
From: Toby Thain @ 2010-04-26 23:19 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, openvpn-users
On 27-Apr-10, at 1:58 AM, Karl O. Pinc wrote:
> On 04/26/2010 10:23:21 AM, David Sommerseth wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 26/04/10 16:47, Karl O. Pinc wrote:
>>> Speaking of the standard release process there is still this
>> thread:
>>>
>>> Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems
>> building
>>
>>> 2.1 rc15 on Windows XP
>>>
>>> and its patch for releasing unpackaged MS Windows binaries;
>>> quite similar to what you're proposing for OS/X.
>
>> Thanks for pushing this. I am honestly not quite sure were we stand
>> with that patch. And since I understand the Windows building least
>> of
>> all, I've refrained from going into details of this one so far. It
>> has
>> not been my intention of ignoring this patch. I'm primarily focusing
>> on
>> the platforms I happen to understand better, and hope others will
>> chime
>> in on the other issues.
>>
>> But as responses are missing, I'll try to find some time in the near
>> future (this week is crazily hectic for me) - to see if I can
>> understand
>> what your patch solves. That is a little bit unclear to me, as the
>> patch I'm looking at seems to just make a tarball with compiled
>> binaries
>> ... Right now, I do not immediately see what problem that solves.
>> But
>> I'm pretty sure I'm overlooking something!
>>
>> Btw, you mentioned in some of the threads that you would look at some
>> of
>> the docs for this as well. I remember vaguely something about
>> another
>> set of patches for HTML files - which I can't say I've seen in the
>> source tree. That would be good to get into the tree together with
>> this
>> patch when I've looked at it a bit better.
>
> It's a packaging policy issue.
>
> The problem addressed is that there only binaries available
> for MS Windows are pre-packaged in an installer executable.
> This means that anyone who wants stock binaries but a
> modified installer has to recompile from source.
>
> There are many reasons why one would want a non-stock
> MS Windows installer -- the foremost being to include
> an OpenVPN configuration file that allows connections
> between pre-designated endpoints. One might want to
> go so far as to include certificates in the installation
> to secure the communications channel. ;-)
For the OS X package, I chose to simply make two packages - one the
generic binaries, and one for whatever configuration and keys are
needed for a particular deployment. Could you do the same on Windows?
> Creating custom installation executables is
> relatively easy, especially as the OpenVPN code base
> includes a working config file that's used to make
> the installer OpenVPN distributes. But of course
> OpenVPN binaries are a requirement before packaging
> can be attempted.
>
> Recompiling is both complicated and error prone. Historically
> there are a number of issues that make compiling difficult.
> I recall problems with mingw versions
> when compiling on MS Windows and some other sort of problems
> when trying to cross compile from Linux.
Just a FYI - the Visual Studio Express toolchain (32+64 bit) works
well under WINE.
> In any case it's
> clear that compiling will always be relatively complicated
> and time-consuming to setup in comparison with downloading
> binaries.
Correct - while it is a lot easier on OS X (just ./configure; make),
most users never install the Developer Tools and don't know how to use
Terminal. So we have similar motivations.
>
> So, there are 2 patches. The first is to the OpenVPN
> build process. It produces unpackaged MS Windows binaries
> and (last you wrote) it works. The second patch is to
> the OpenVPN documentation. It documents that the
> binaries exist and when you want them. It does not
> apply because the OpenVPN website has since been
> restructured. The doc patch needs to be re-worked
> to put the text in the appropriate place.
>
> But this only makes sense if OpenVPN _will_ release
> unpackaged MS Windows binaries. It makes sense to me;
> the project is already releasing unpackaged Linux
> binaries and it now talking about doing the same
> for OS/X binaries.
I don't think unpackaged OS X binaries are very useful, which is why I
created the pkg+dmg. I haven't explored whatever GUI & packaging
enhancements have been done by third parties - overkill for my
immediate simple deployment needs.
I *do* think that generic OS X binary pkgs are worthwhile including as
part of the standard downloads.
--Toby
> There's clear utility. Regardless,
> this is a policy decision. Getting a resolution on
> packaging policy seems to me to be the first step.
>
> If OpenVPN _won't'_ release unpackaged MS Windows
> binaries I'd like to know why so it would be
> nice if whomever moves this forward, as with
> any other patch, solicits more than a yes/no answer.
>
> Regards,
>
> Karl <kop@...1206...>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 19:11 ` Karl O. Pinc
2010-04-26 23:02 ` David Sommerseth
@ 2010-04-26 23:31 ` Toby Thain
2010-04-27 4:04 ` Karl O. Pinc
2 siblings, 0 replies; 24+ messages in thread
From: Toby Thain @ 2010-04-26 23:31 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, Peter Stuge <peter@
On 27-Apr-10, at 5:11 AM, Karl O. Pinc wrote:
> On 04/26/2010 11:53:19 AM, Peter Stuge wrote:
>> Karl O. Pinc wrote:
>>> the project is already releasing unpackaged Linux
>>> binaries
>>
>> Really?
>
> They seem to have stopped sometime after July 30 2008.
>
> http://web.archive.org/web/20080730205524/openvpn.net/index.php/
> downloads.html
>
> It's hard to tell when because archive.org does not appear
> to be allowed to archive the site any longer. Or at least
> there's nothing more recent. (This seems silly. I wonder why.)
>
> (I clearly haven't been downloading binaries in a while.
> Probably because I rely on my distro for binaries so
> they can do the systems integration and security patches,
> or I am getting development from CVS/git.
>
> IMO people who don't rely on their distro for systems integration
> and security patches are asking for trouble. There are of course
> always reasons to make specific exceptions, RH comes to mind. :)
>
> Is OpenVPN in RHEL6?)
>
>>
>>> and it now talking about doing the same for OS/X binaries.
>>
>> Recently discussed work for contrib/ produces a .dmg, very much a
>> package in my view.
>
> Ok. I don't know much about .dmg. I thought they were basically
> tarballs by another name in that they just stick stuff somewhere.
> My Mac usage is sporadic, sorry.
The Makefile produces both 'pkg' and 'dmg'. Dmg is just an OS X
standard self-mounting single file archive which is a way of
distributing the pkg. Generating a dmg is useful because the pkg is
actually a file tree, not a single file, so inappropriate for
downloading, attaching, etc.
Pkg is the package itself, which like any binary UNIX package is
indeed a tarball by another name plus some metadata and scripts - but
of course infinitely easier for non-technical end users (let alone
compared to a source build).
--Toby
>
>>
>>
>>> There's clear utility.
>>
>> I guess it depends. I'm not sure that I agree that compilation is a
>> much bigger bother than (cross-)compiling the NSIS installer..
>
> On Debian all I had to do was "aptitude install nsis" and then
> run it to make MS Windows installers. Plug and play, no
> compiling necessary.
>
> Regards,
>
> Karl <kop@...1206...>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 23:19 ` Toby Thain
@ 2010-04-27 2:19 ` Karl O. Pinc
2010-04-27 2:46 ` Toby Thain
0 siblings, 1 reply; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-27 2:19 UTC (permalink / raw)
To: Toby Thain <toby@; +Cc: openvpn-devel, openvpn-users
On 04/26/2010 06:19:31 PM, Toby Thain wrote:
>
> On 27-Apr-10, at 1:58 AM, Karl O. Pinc wrote:
> >
> > The problem addressed is that there only binaries available
> > for MS Windows are pre-packaged in an installer executable.
> > This means that anyone who wants stock binaries but a
> > modified installer has to recompile from source.
>
> For the OS X package, I chose to simply make two packages - one the
> generic binaries, and one for whatever configuration and keys are
> needed for a particular deployment. Could you do the same on Windows?
Sure, but this greatly increases the complexity for the
end-user. Just adding another installer at least doubles the
complexity. A custom install can be one-click. The stock
OpenVPN installer (last I looked) presented the user
with many choices and is far more complex than a 1-click
install.
Getting the users to do anything at all can be tricky
(especially at the outlying ends of the pay scale).
The less that can go wrong the better.
> > But this only makes sense if OpenVPN _will_ release
> > unpackaged MS Windows binaries. It makes sense to me;
> > the project is already releasing unpackaged Linux
> > binaries and it now talking about doing the same
> > for OS/X binaries.
>
> I don't think unpackaged OS X binaries are very useful, which is why
> I
>
> created the pkg+dmg.
I agree, because the Apple development kit is shipped,
if not installed, on every Mac. (Last I looked.) And
because ./configure ; make is painless. MS Windows on
the other hand requires additional software
to compile anything. And the FOSS choices, which
are the the ones most universally available, are non-trivial
to install and use.
I'd bet cross compiling Un*x-to-Mac is easier too, but
I have no experience to back that up.
Now that OpenVPN is accepting more patches cross compiling
Un*x-to-MSWindows will probably get easier but it will
never be easy.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 23:02 ` David Sommerseth
@ 2010-04-27 2:25 ` Karl O. Pinc
0 siblings, 0 replies; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-27 2:25 UTC (permalink / raw)
To: David Sommerseth <openvpn.list@; +Cc: openvpn-devel, Peter Stuge <peter@
On 04/26/2010 06:02:46 PM, David Sommerseth wrote:
> On 26/04/10 21:11, Karl O. Pinc wrote:
> > On Debian all I had to do was "aptitude install nsis" and then
> > run it to make MS Windows installers. Plug and play, no
> > compiling necessary.
> >
>
> Just a little nitpick, when you run makensis, that's actually
> compilation of the installer - even when you're doing it on Linux.
> You
> get a Windows binary as the result.
As long as we're nitpicking... ;-)
That's interesting. I figured the nsis install scripts
were interpreted and, if I thought about it at all,
running makensis setup some data structures and did
some linking.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-27 2:19 ` Karl O. Pinc
@ 2010-04-27 2:46 ` Toby Thain
2010-04-27 3:03 ` Toby Thain
2010-04-27 3:54 ` Karl O. Pinc
0 siblings, 2 replies; 24+ messages in thread
From: Toby Thain @ 2010-04-27 2:46 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, openvpn-users
On 27-Apr-10, at 12:19 PM, Karl O. Pinc wrote:
> On 04/26/2010 06:19:31 PM, Toby Thain wrote:
>>>
>>>
>>
>> I don't think unpackaged OS X binaries are very useful, which is why
>> I
>>
>> created the pkg+dmg.
>
> I agree, because the Apple development kit is shipped,
> if not installed, on every Mac.
It ships on the DVD but most people never install it, of course.
> (Last I looked.) And
> because ./configure ; make is painless.
To use your argument from above -- imho much too complex for most end
users. As well as requiring Apple Developer Tools (they have to go
find the original DVD, which may or may not even be possible), this
involves locating and downloading two source archives from two
different sites, and configuring and building them both; beyond the
pale for non-technical users, even though it's trivial for "us".
The pkg/dmg is, on the other hand, a genuine one click install. (Even
if you have to do a 2nd key install, which pkg has to be built
individually and distributed securely anyway.)
It seems logical to me that an OS X binary dmg could be on the OpenVPN
downloads page, giving a similar level of convenience to "yum install
openvpn" or "apt-get install openvpn" or "emerge openvpn".
One thing that should *not*, in my opinion, be encouraged at all by
OpenVPN, are third party package managers (MacPorts, Fink, Homebrew
etc) as the binary route on OS X. That seems to do more harm than good.
> MS Windows on
> the other hand requires additional software
> to compile anything. And the FOSS choices, which
> are the the ones most universally available, are non-trivial
> to install and use.
>
> I'd bet cross compiling Un*x-to-Mac is easier too, but
> I have no experience to back that up.
Generally very simple, fwiw. It probably helps that OS X toolchain is
gcc-based and many GNU utilities are standard.
> Now that OpenVPN is accepting more patches cross compiling
> Un*x-to-MSWindows will probably get easier but it will
> never be easy.
If I were deploying it, rather than hacking on it, I would expect a
binary installer to be available for my platform, at http://openvpn.net
--Toby
>
> Karl <kop@...1206...>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-27 2:46 ` Toby Thain
@ 2010-04-27 3:03 ` Toby Thain
2010-04-27 3:54 ` Karl O. Pinc
1 sibling, 0 replies; 24+ messages in thread
From: Toby Thain @ 2010-04-27 3:03 UTC (permalink / raw)
To: openvpn-devel, openvpn-users
On 27-Apr-10, at 12:46 PM, Toby Thain wrote:
>
> On 27-Apr-10, at 12:19 PM, Karl O. Pinc wrote:
>
>> On 04/26/2010 06:19:31 PM, Toby Thain wrote:
>>>>
>>>>
>>>
>>> I don't think unpackaged OS X binaries are very useful, which is why
>>> I
>>>
>>> created the pkg+dmg.
>>
>> I agree, because the Apple development kit is shipped,
>> if not installed, on every Mac.
>
> It ships on the DVD but most people never install it, of course.
>
>> (Last I looked.) And
>> because ./configure ; make is painless.
>
> To use your argument from above -- imho much too complex for most end
> users. As well as requiring Apple Developer Tools (they have to go
> find the original DVD, which may or may not even be possible), this
> involves locating and downloading two source archives from two
> different sites, and configuring and building them both;
I left out some other items that the package includes:
– the XML service metadata (plist) that doesn't exist in the source
distribution
– launchd service setup
So it's really well beyond the "end user" realm...
(More details: http://telegraphics.com.au/svn/openvpn-package/trunk/README
)
This is probably solved in other ways by 3rd party OpenVPN derivatives
out there, but imho there should still be an 'official' binary
installer.
--Toby
> beyond the
> pale for non-technical users, even though it's trivial for "us".
>
> The pkg/dmg is, on the other hand, a genuine one click install.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-27 2:46 ` Toby Thain
2010-04-27 3:03 ` Toby Thain
@ 2010-04-27 3:54 ` Karl O. Pinc
2010-04-27 4:39 ` Toby Thain
2010-04-27 10:58 ` Peter Stuge
1 sibling, 2 replies; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-27 3:54 UTC (permalink / raw)
To: Toby Thain <toby@; +Cc: openvpn-devel, openvpn-users
On 04/26/2010 09:46:06 PM, Toby Thain wrote:
>
> On 27-Apr-10, at 12:19 PM, Karl O. Pinc wrote:
>
> > On 04/26/2010 06:19:31 PM, Toby Thain wrote:
> >>>
> >>>
> >>
> >> I don't think unpackaged OS X binaries are very useful, which is
> why
> >> I
> >>
> >> created the pkg+dmg.
> >
> > I agree, because the Apple development kit is shipped,
> > if not installed, on every Mac.
>
> It ships on the DVD but most people never install it, of course.
>
> > (Last I looked.) And
> > because ./configure ; make is painless.
>
> To use your argument from above -- imho much too complex for most end
>
> users. As well as requiring Apple Developer Tools (they have to go
> find the original DVD, which may or may not even be possible), this
> involves locating and downloading two source archives from two
> different sites, and configuring and building them both; beyond the
> pale for non-technical users, even though it's trivial for "us".
I'm not following you here. I thought we were talking about whether
unpackaged OS/X binaries were useful to anybody. The answer being
no because developers and packagers are the only people who need
them and developers and packagers can easily create OS/X binaries.
>
> The pkg/dmg is, on the other hand, a genuine one click install. (Even
>
> if you have to do a 2nd key install, which pkg has to be built
> individually and distributed securely anyway.)
Depending on the degree of security required it could be enough
to key the server but not the client. It does not matter to
my argument though, if you're going to make individualized packages
for each user you may as well put everything required into
the package you supply. Having to compile binaries for MS Windows
becomes a big sticking point when making an all-inclusive MS
Windows installer; because you're already making an installer
you know how to do that and you've got a working example
of the OpenVPN installer as a starting point.
> It seems logical to me that an OS X binary dmg could be on the
> OpenVPN
>
> downloads page, giving a similar level of convenience to "yum install
>
> openvpn" or "apt-get install openvpn" or "emerge openvpn".
Sure. Packages can be useful to end-users.
>
> One thing that should *not*, in my opinion, be encouraged at all by
> OpenVPN, are third party package managers (MacPorts, Fink, Homebrew
> etc) as the binary route on OS X. That seems to do more harm than
> good.
I have no opinion. I suppose it depends on the degree of systems
integration provided by the 3rd party. I assume this is usually
none, in which case there's no point and the end-user may as well
get their packages straight from the source.
>
>
> If I were deploying it, rather than hacking on it, I would expect a
> binary installer to be available for my platform, at
> http://openvpn.net
I'd expect my distro provider to supply it, be sure it integrates
with everything else, and support security fixes. YMMV.
Of course this assume a distro. Users of commercial OSs
are generally expected to arrange for their own systems
integration and application support. In that case the
typical user should follow your advice and get their
packages direct from OpenVPN.
Which raises another issue. IMO OpenVPN is encouraging
bad practices by supplying packages for distros that
include OpenVPN. The typical user is more likely to have
a bad OpenVPN experience, over time, when using packages
obtained directly from OpenVPN than when using packages
created by their distro, for the reasons outlined above
and earlier in this thread. Some people may benefit
from having the most recent OpenVPN and obtaining it
straight from the project, but these people are also
the most likely to be able to package it themselves.
If this is all true then the OpenVPN project is doing
it's userbase a dis-service by making, say, packages
for Red Hat available for download because this is
tacit encouragement of bad practice. At minimum
there should be a warning to educate the naive user.
The situation is different for MS Windows and OS/X.
Packages are needed for those platforms and whatever
other commercial OSs the project wants to support.
There. Now I've wandered far from the original
topic and likely offended someone too.
Mission accomplished. :-P
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 19:11 ` Karl O. Pinc
2010-04-26 23:02 ` David Sommerseth
2010-04-26 23:31 ` Toby Thain
@ 2010-04-27 4:04 ` Karl O. Pinc
2 siblings, 0 replies; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-27 4:04 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, Peter Stuge <peter@
On 04/26/2010 02:11:26 PM, Karl O. Pinc wrote:
> On 04/26/2010 11:53:19 AM, Peter Stuge wrote:
> > Karl O. Pinc wrote:
> > > the project is already releasing unpackaged Linux
> > > binaries
> >
> > Really?
>
> They seem to have stopped sometime after July 30 2008.
>
> http://web.archive.org/web/20080730205524/openvpn.net/index.php/
> downloads.html
Sheesh Peter, you are right. That pages has source downloads
and a MS Windows installer. And it's the same page I recall
seeing forever.
Nothing anywhere about non-MSWindows binaries.
I completely mis-remembered, and didn't even see my mistake
when I called up the old page. Sorry about that.
I seem to be making a habit of making false statements
on this list. I'll see if I can fix that.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-27 3:54 ` Karl O. Pinc
@ 2010-04-27 4:39 ` Toby Thain
2010-04-27 10:58 ` Peter Stuge
1 sibling, 0 replies; 24+ messages in thread
From: Toby Thain @ 2010-04-27 4:39 UTC (permalink / raw)
To: "Karl O. Pinc" <kop@; +Cc: openvpn-devel, openvpn-users
On 27-Apr-10, at 1:54 PM, Karl O. Pinc wrote:
> On 04/26/2010 09:46:06 PM, Toby Thain wrote:
>>
>> On 27-Apr-10, at 12:19 PM, Karl O. Pinc wrote:
>>
>>> On 04/26/2010 06:19:31 PM, Toby Thain wrote:
>>>>>
>>>>>
>>>>
>>>> I don't think unpackaged OS X binaries are very useful, which is
>> why
>>>> I
>>>>
>>>> created the pkg+dmg.
>>>
>>> I agree, because the Apple development kit is shipped,
>>> if not installed, on every Mac.
>>
>> It ships on the DVD but most people never install it, of course.
>>
>>> (Last I looked.) And
>>> because ./configure ; make is painless.
>>
>> To use your argument from above -- imho much too complex for most end
>>
>> users. As well as requiring Apple Developer Tools (they have to go
>> find the original DVD, which may or may not even be possible), this
>> involves locating and downloading two source archives from two
>> different sites, and configuring and building them both; beyond the
>> pale for non-technical users, even though it's trivial for "us".
>
> I'm not following you here. I thought we were talking about whether
> unpackaged OS/X binaries were useful to anybody. The answer being
> no because developers and packagers are the only people who need
> them and developers and packagers can easily create OS/X binaries.
Ah, okay, then we are in agreement.
>
>> ...
>
>> It seems logical to me that an OS X binary dmg could be on the
>> OpenVPN
>>
>> downloads page, giving a similar level of convenience to "yum install
>>
>> openvpn" or "apt-get install openvpn" or "emerge openvpn".
>
> Sure. Packages can be useful to end-users.
Right - or those organising deployments to them.
>
>>
>> One thing that should *not*, in my opinion, be encouraged at all by
>> OpenVPN, are third party package managers (MacPorts, Fink, Homebrew
>> etc) as the binary route on OS X. That seems to do more harm than
>> good.
>
> I have no opinion. I suppose it depends on the degree of systems
> integration provided by the 3rd party. I assume this is usually
> none, in which case there's no point and the end-user may as well
> get their packages straight from the source.
>
>>
>>
>> If I were deploying it, rather than hacking on it, I would expect a
>> binary installer to be available for my platform, at
>> http://openvpn.net
>
> I'd expect my distro provider to supply it, be sure it integrates
> with everything else, and support security fixes. ... The typical
> user is more likely to have
> a bad OpenVPN experience, over time, when using packages
> obtained directly from OpenVPN than when using packages
> created by their distro, for the reasons outlined above
> and earlier in this thread. ...
>
> The situation is different for MS Windows and OS/X.
> Packages are needed for those platforms and whatever
> other commercial OSs the project wants to support.
+1
Solaris 10 is another possibility. I have experience with this package
flavour and could easily do the same job as I did for OS X, for
contrib, at least, if not binary pkg.
>
> There. Now I've wandered far from the original
> topic and likely offended someone too.
Certainly not me.
--Toby
> Mission accomplished. :-P
>
> Regards,
>
>
> Karl <kop@...1206...>
> Free Software: "You don't pay back, you pay forward."
> -- Robert A. Heinlein
>
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-27 3:54 ` Karl O. Pinc
2010-04-27 4:39 ` Toby Thain
@ 2010-04-27 10:58 ` Peter Stuge
2010-04-27 15:26 ` Karl O. Pinc
2010-04-28 15:42 ` Karl O. Pinc
1 sibling, 2 replies; 24+ messages in thread
From: Peter Stuge @ 2010-04-27 10:58 UTC (permalink / raw)
To: openvpn-devel
Karl O. Pinc wrote:
> IMO OpenVPN is encouraging bad practices by supplying packages for
> distros that include OpenVPN.
Ideally the package for that distro as made by OpenVPN is always
equivalent to the one made by the distributor.
What do I mean? I mean that I'm happy with .spec files and the likes,
that make up the source code for a particular kind of binary package,
being committed upstream.
And if they are, then it's of course fairly easy for upstream to use
them, and to make packages which are at the very least compatible
with the distribution.
And, I think that since it is downloaded from a site other than the
distributor's, users who actually do grab packages "manually" will be
able to tell the difference from a package delivered by the
distributor.
//Peter
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-27 10:58 ` Peter Stuge
@ 2010-04-27 15:26 ` Karl O. Pinc
2010-04-28 15:42 ` Karl O. Pinc
1 sibling, 0 replies; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-27 15:26 UTC (permalink / raw)
To: Peter Stuge <peter@; +Cc: openvpn-devel
On 04/27/2010 05:58:43 AM, Peter Stuge wrote:
> Karl O. Pinc wrote:
> > IMO OpenVPN is encouraging bad practices by supplying packages for
> > distros that include OpenVPN.
>
> Ideally the package for that distro as made by OpenVPN is always
> equivalent to the one made by the distributor.
>
> What do I mean? I mean that I'm happy with .spec files and the likes,
> that make up the source code for a particular kind of binary package,
> being committed upstream.
>
> And if they are, then it's of course fairly easy for upstream to use
> them, and to make packages which are at the very least compatible
> with the distribution.
I agree.
It is useful for OpenVPN to distribute .spec files and
equivalents for use by disto packagers.
>
> And, I think that since it is downloaded from a site other than the
> distributor's, users who actually do grab packages "manually" will be
> able to tell the difference from a package delivered by the
> distributor.
The question is not whether users can tell the difference, it's
whether users know enough to know the advantages of getting
their packages from their distro. I believe that most users
are unaware of these advantages because they have experience
only with OSs that force them to arrange for their own
systems integration. IMO the widespread failure to integrate disparate
software and the consequent gradual degradation of so many systems,
often ending in a disk wipe and OS re-install, demonstrates
the extent of the problem. While OpenVPN's users are clearly
the cream of the crop, hip, techo-savvy, and sporting
shiny white smiles, I don't believe they are immune
and the OpenVPN project should encourage them to make
good choices. This would help toward a good long-term
OpenVPN experience. The current policy that makes
pre-packaged downloads available without explanation
does nothing to encourage good sysadmin practice and
puts a bad choice one click away.
Giant problem? No. They'll always be plenty of ways
to make bad choices. I'd be ok with making distro specific packages
available so long as you also tell the end-user they are
probably better off without them. :)
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-27 10:58 ` Peter Stuge
2010-04-27 15:26 ` Karl O. Pinc
@ 2010-04-28 15:42 ` Karl O. Pinc
1 sibling, 0 replies; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-28 15:42 UTC (permalink / raw)
To: Peter Stuge <peter@; +Cc: openvpn-devel
On 04/27/2010 05:58:43 AM, Peter Stuge wrote:
> Karl O. Pinc wrote:
> > IMO OpenVPN is encouraging bad practices by supplying packages for
> > distros that include OpenVPN.
>
> Ideally the package for that distro as made by OpenVPN is always
> equivalent to the one made by the distributor.
I'm writing again in case someone thinks this is a reason why it's
fine for an end-user to get their OpenVPN from openvpn.net.
The problem is not the initial package installation. It's
keeping up with changes over time. That's the big
service that distro's provide. Installing a single non-distro
application is no big deal. More than a few become a problem
to keep up with to the point where eventually things stop
working. Packages makes it easier to keep track of what's
what and keep things updated, in comparison to ./configure;
make; make install, but the point of diminishing returns
is soon reached regardless.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1)
2010-04-26 15:23 ` [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1) David Sommerseth
2010-04-26 15:58 ` Karl O. Pinc
@ 2010-04-29 3:04 ` Karl O. Pinc
1 sibling, 0 replies; 24+ messages in thread
From: Karl O. Pinc @ 2010-04-29 3:04 UTC (permalink / raw)
To: David Sommerseth <openvpn.list@; +Cc: openvpn-devel, openvpn-users
On 04/26/2010 10:23:21 AM, David Sommerseth wrote:
> On 26/04/10 16:47, Karl O. Pinc wrote:
> >
> > Speaking of the standard release process there is still this
> thread:
> >
> > Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems
> building
> > 2.1 rc15 on Windows XP
> >
> > and its patch for releasing unpackaged MS Windows binaries;
> > quite similar to what you're proposing for OS/X. There has been
> > no response from this list regarding this for quite some
> > time despite repeated requests, unless I missed something
> > somewhere along the line.
For reference I'm linking to the original thread here.
http://thread.gmane.org/gmane.network.openvpn.devel/2566/focus=3171
I wrote Samuli Seppänen to get this link added to the trac
entry for the upcoming IRC meeting as further reference,
or alternately to get access to trac.
(The parent of this thread, before the subject was changed,
is an agenda item but there's no reference to
the prior thread.) I have not heard
back so am writing here to be sure the link is available
to anyone who needs it for the meeting.
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2010-04-29 3:04 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-25 23:47 [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1 Toby Thain
2010-04-26 8:42 ` Arnoud Vermeer
2010-04-26 14:47 ` Karl O. Pinc
2010-04-26 15:23 ` [Openvpn-devel] Unpackaged Windows binaries (Was: Re: [Openvpn-users] [ANN] OS X packages - OpenVPN 2.1.1) David Sommerseth
2010-04-26 15:58 ` Karl O. Pinc
2010-04-26 16:53 ` Peter Stuge
2010-04-26 19:11 ` Karl O. Pinc
2010-04-26 23:02 ` David Sommerseth
2010-04-27 2:25 ` Karl O. Pinc
2010-04-26 23:31 ` Toby Thain
2010-04-27 4:04 ` Karl O. Pinc
2010-04-26 23:19 ` Toby Thain
2010-04-27 2:19 ` Karl O. Pinc
2010-04-27 2:46 ` Toby Thain
2010-04-27 3:03 ` Toby Thain
2010-04-27 3:54 ` Karl O. Pinc
2010-04-27 4:39 ` Toby Thain
2010-04-27 10:58 ` Peter Stuge
2010-04-27 15:26 ` Karl O. Pinc
2010-04-28 15:42 ` Karl O. Pinc
2010-04-29 3:04 ` Karl O. Pinc
2010-04-26 11:34 ` [Openvpn-devel] [ANN] OS X packages - OpenVPN 2.1.1 David Sommerseth
2010-04-26 12:08 ` Toby Thain
2010-04-26 12:47 ` David Sommerseth
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.