3-Nov-98 09:37 you wrote:
> So far mod_ssl can only be built with apache sources. I've tanken a look at
> mod_php3 and it can be built without the apache sources (just the header
> files).
Yes, but mod_php3 is HORRIBLE here. Right sample would be mod_perl 1.15 or
1.17 (mod_php3 does not use options stored in apxs and thus compiling of php3
in SSL-aware Apache is little tricky). In mod_perl 1.15_01 and 1.16 there are
small error exactly in DSO support :-((
> Is there any way to build mod_ssl as a module without having the apache
> sources.
No and not planned in near future.
> I think it would be very useful when building RPMs.
Unfortunatelly it's not possible -- it's not technical question but rather
political one :-((
> I think in mod_php3 they use something called apaci (I'm not familiar with
> this).
Not apaci but apxs of course and as you could guess a lot of peoples here
(including Ralf who is more familiar then most of us :-)) knows a lot about
apaci and apxs...
> Is anything similar planned for mod_ssl?
More or less. Something is done in 2.1.b7...
> I'd love just to install mod_ssl to my existing apache installation, and
> not installing a complete new apache.
It's not possible.
> Are there any cons against this approach?
Exactly one but GIANT one: such hooks will make Apache non-exportable from US
and thus will lead to split in Apache development. This is completely
unappropriate. You could grab 2.1.b8 and create two RPMs : one with patched
Apache and one with mod_ssl DSO (I am plan to do this when I'll have spare
time :-) But you could not add mod_ssl in unpatched Apache in any way :-((
It was discussed here many times...
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
