On Fri, Oct 30, 1998, Trung Tran-Duc wrote:
> > > Email over the exe and I'll create a self-extracting exe for you. Just let
> > > me know where it should default (expand) to.
> >
> > Oh, I was not precise enough. What I actually want is not only a
> > self-extracting program. My favorite would be that when I run patch.exe it
> > extracts itself (in memory on in current working dir) and immediately runs
> > itself. So I can use the packed patch.exe similar to the unpacked patch.exe.
> > At least under my C64 times the years ago this was common practice. Exists
> > such stuff for Windows NT? Or did I misunderstand you and you mean exactly
> > this? Then it should unpack into the current working directory because this is
> > maximum portable, IMHO.
>
> Ralf, I don't see your point here. Why do you want to compress the
> patch.exe file? The tarball distribution is a compressed file itself.
> Do you have difficulty putting binary file into CVS?
No, CVS is not the problem. You're right: Now I can't see the point here any
longer myself. Please forget my silly request, I totally forgot the .gz of
.tar.gz. Seems like my aesthetic eye was just a little bit waggly after
seeing a 120KB Windows .exe in my small Unix source tree ;-)
> I notice you have patch's source files in ./etc and compile and run it
> for UNIX platforms. Can we do the same for Win32? The user must have
> the C compiler in any case. I can prepare the makefile and modify
> Configure.bat accordingly.
Yes, this would be my preferred approach: Having _ONE_ patch 2.5 source tree
which compiles both under Unix and Win32 _AND_ is stripped down the minimum
size. But the Windows sources I found for patch 2.5 didn't worked under Unix
and the Unix sources not under Windows. And they were not stripped down to the
minimum files.
So, the best would be (my wish) just this:
Makefile.in
Makefile.win
config.h.in
configure
patch.c
patch.h
i.e. someone should take patch 2.5, strip it down to only those files and
integrate the Win32 port. This way the mod_ssl distribution gets very small
again and the patch is what it is also in size: just a little helper tool.
Is someone interested in contributing this to mod_ssl?
BTW, it would be a valueable thing for more projects than mod_ssl... Actually
we could use this for the other Apache modules which have to patch
sources, too.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
