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


Reply via email to