> My final vision is to have an integrated source tree, including sub
> trees for Apache (including EAPI patches), PHP4, JServ (Jakarta?),
> Perl, OpenSSL, mod_perl, etc., with one simple command (like the
> "src/helpers/binbuild.sh"), that will build everything, without an
> installation process of zillion steps. You may look at this package
> as a Linux distribution, and the sub-tree of Apache as the kernel
> in the above distribution (I hope you understood the analogy).
This does not sound like something I would want to download on a slow
modem.
It would either be huge beyond immagination or it would be far from
complete. The final executable would also be much larger than necessary.
Of the Apache installations I've done over the last couple of years,
I've never wanted one with that meny features compiled in at the same
time - even on my own development machine I usually prefer to have
different versions of apache for different purposes. In production
servers I really would consider it "a bad thing"(tm) to compile it
with anything that isn't needed, not to mention that there's always
things that need to be compiled differently on different platforms.
IMO it would be a much better idea to document the compile/build
process of some of the more common Apache installations. Or perhaps
to build sort of an interactive configuration system much like the
setup file from php that collects options for configure.
>
> But this ambitious vision, can start with a small step, by
> integrating the mod_ssl patches into "our" own source tree of
> Apache, and supplying the patched source tree to users, rather than
> the patches separately.
>
One problem is that AFAIK mod_ssl not only applies patches, it also
sets makefile options and etc when patching - which might end up
having a patched source tree, that would need to be patched again
to set all the options (like library locations etc.)
Anyway, not all the Apache installations we do around here need
ssl - so that would have me downloading the Apache source twice
(all right, it really isn't like a few megs more would make a
noticable difference to me ;-) but it would add an extra 1.4M to
the traffic at modssl.org for every apache-mod_ssl download.
> If you love this idea, I suggest to start it with 2.5.0-1.3.10
> (assuming that 1.3.10 will be rolled on the 19th, or a few days
> after). This change deserves (IMHO) a new major release number.
I'm not really sure that it would be necessary - having to keep up
with the changes that happen in the Apache tree would probably
make it a lot easier to just keep doing the development as it has
always been done with a seperate mod_ssl tree, and then applying
mod_ssl before distribution.
vh.
Mads Toftum, MT165-RIPE
---
"No, I'm not going to explain it. If you can't figure it out,
you didn't want to know anyway..." --Larry Wall
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
