The answer is very simple. All the modules you mentioned (e.g. PHP)
are separate modules. They can (and should) be built out of the
tree of Apache. Even if you choose to build them in the source tree
of Apache, you should do it at least in the separate directory
"src/modules/extra", or by putting them in an independent directory
of you and adding "--add-module" to the configuration command of
Apache. So if you work in the "Right-Way"(TM), there should not be
any conflict.
Moreover, one of the motivations (which I didn't mention in my
previous message due to lack of space and time), is the ease of
merging YOUR stuff with a newer version of mod_ssl. When you have a
module which is not only a module but makes some modifications in
the original source tree of Apache, there is a high chance that the
patch scripts of mod_ssl will fail to work on the modified sources
of Apache. I develop such a project, and it is a nightmare for me.
I found it EASIER to merge my patches from an old version of the
patched tree of Apache (with mod_ssl patches) to a newer one, than
to deal with the patch scripts. Actually, the only way that I can
(without spending too much effort) to "upgrade" my stuff, is by
merging the original (Apache + mod_ssl applied into + my stuff
applied into) with the newer (Apache + mod_ssl applied into).
So even in the case of modules which are not separate, my
experience showed me that it was better to have a ready tree than
patch scripts.
Cliff Woolley wrote:
>
> >>> Eli Marmor <[EMAIL PROTECTED]> 12/11/99 06:33PM >>>
> >Providing mod_ssl as a patched Apache source tree, instead of a
> >separate patch.
>
> On the other hand, for current users of mod_ssl it'd be nice to just
> have a patch against the previous version of mod_ssl's *already patched
> source tree*. For example, if I run mod_ssl 2.4.8's patches against a
> clean Apache 1.3.9 source tree and then add other packages to the Apache
> tree (JServ, mod_php, mod_fastcgi, etc), it's annoying to have to start
> all over again when mod_ssl 2.4.9 comes out. It'd be nice to just have
> the things that changed between mod_ssl 2.4.8 and 2.4.9 as a patch so
> that I could apply that to my already-configured tree and know that all
> the patches will apply correctly. I know that most of the time you can
> do this anyway because the EAPI doesn't change very often (it actually
> *did* work for the 2.4.8->2.4.9 upgrade, for example), but when it
> doesn't work and you get *.rej files in your Apache source tree, the
> problems that ensue can be confusing. I know it's bitten me before!
>
> So what if a complete distribution of a pre-patched Apache source tree
> were offered for first-time users and a patch upgrade from the previous
> version of Apache+mod_ssl were offered for existing users?
>
> Does that make sense? I know I could make the above-mentioned diff on
> my own in a separate location and then apply it to my main Apache source
> tree, but I imagine I'm not the only one that would want it, which is
> why I bring it up. What do you all think, is all this just too much
> work?
>
> --Cliff
--
Eli Marmor
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
