From: "Karl O. Pinc" <kop@...1206...>
To: David Sommerseth <openvpn.list@...1114...>
Cc: openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP
Date: Sun, 28 Feb 2010 21:48:46 -0600 [thread overview]
Message-ID: <1267415326.30675.1@...1207...> (raw)
In-Reply-To: <4B8A614A.4020406@...1114...> (from openvpn.list@...1114... on Sun Feb 28 06:27:54 2010)
On 02/28/2010 06:27:54 AM, David Sommerseth wrote:
> On 09/04/09 05:03, Karl O. Pinc wrote:
<snip>
> > The OpenVPN devs have a "built" source tree in which they run
> > install-win32/buildinstaller. My point being that
> > if they would package it up
> > and release it alongside the resultant installer
> > none of these sorts of issues would ever come up.
> >
> > Attached is a patch that produces a un-nsis-installer
> > windows binary release as part of the build process.
> >
> > Apply it with:
> >
> > cd openvpn
> > patch -p1 < buildbinaryrelease.patch
> >
> > The result is a file named something like:
> > openvpn-2.1_rc15-winbinaries.tar.gz
> >
> > I deliberately produce a tar.gz file
> > rather than a zip file to keep
> > Windows people from downloading it accidentally
> > instead of the Windows installer exe.
> >
> > There is more work to be done. The file needs to
> > be signed and put on the website every time there's
> > a release. I don't see anything in svn to patch
> > that would aid this process.
>
> Hi!
>
> I'm going through the mailing list, picking up patches which seems
> not
> to be included. Is this patch still interesting to get included?
I would like to see it included.
The goal is to allow people to create
custom installers for MS Windows without having to rebuild
the source or cross compile. The point of the patch
is to support an "unpackaged" release of the MS Windows
binaries. In other words raw binaries that are not
part of an installer, which can then be packaged
using the nsis installer to produce a custom install.
As noted above this means that the official OpenVPN project
would have to actually release such binaries. If the
project does not want to do this there is no point in
having the patch.
So, this requires upstream approval. In some ways this
is no different from other patches, except that it requires
ongoing work as new releases come out -- or if not that
then a change to whatever automated process (unavailable to
us, at least at the time the patch was written) that puts
releases out to the public.
> This
> one applies cleanly to the master branch.
>
> I see that this patch is also followed by this one:
>
> <http://article.gmane.org/gmane.network.openvpn.devel/2581>
Yes. The second patch is to the documentation so that people
know what to do with unpackaged MS Windows binaries. Not
much point in releasing the binaries unless there's documentation.
>
> This patch do not apply at all, as the standard checked out tree do
> not
> have INSTALL-win32.html, only INSTALL-win32.txt. Is this correct? I
> can't find this HTML file in the 2.1_rc15 nor 2.1_rc16, which was
> current when this patch was sent to the mailing list.
The OpenVPN site has restructured since this patch was written.
I'd be happy to redo the documentation patch, but I don't see
any point in doing so without some assurance that the effort
will not be wasted. How can I get some feedback on this?
Regards,
Karl <kop@...1206...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
next prev parent reply other threads:[~2010-03-01 3:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 0:58 [Openvpn-devel] Unpackged Windows binaries? -- Problems building 2.1 rc15 on Windows XP Karl O. Pinc
2009-04-08 3:21 ` dave
2009-04-08 3:50 ` Karl O. Pinc
2009-04-08 5:03 ` Karl O. Pinc
2009-04-08 12:58 ` dave
2009-04-08 15:04 ` Karl O. Pinc
2009-04-08 15:23 ` Matt Wilks
2009-04-08 17:02 ` Karl O. Pinc
2009-04-08 17:48 ` Karl O. Pinc
2009-04-08 22:46 ` Alon Bar-Lev
2009-04-09 3:03 ` Karl O. Pinc
2009-04-09 6:01 ` Alon Bar-Lev
2009-04-09 12:58 ` Karl O. Pinc
2009-04-09 17:44 ` Karl O. Pinc
2010-08-27 8:50 ` David Sommerseth
2010-08-27 14:20 ` Karl O. Pinc
2010-08-27 16:16 ` David Sommerseth
2010-08-27 18:19 ` Karl O. Pinc
2010-02-28 12:27 ` David Sommerseth
2010-03-01 3:48 ` Karl O. Pinc [this message]
2010-04-01 15:19 ` Karl O. Pinc
2010-04-20 0:09 ` Karl O. Pinc
2009-04-08 15:10 ` Karl O. Pinc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1267415326.30675.1@...1207... \
--to=openvpn-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.