3-Feb-99 16:56 you wrote:
> On Tue, Feb 02, 1999, Ronan-Yann Lorin wrote:
>> Wouldn't it be nice to have EAPI and mod_ssl available as two distincts
>> distribs ? So we know when EAPI has been changed and we must rebuild apache
>> binary, or when mod_ssl has been changed and we must rebuild mod_ssl DSO.
> Hmmm... it would be nice to have a EAPI dist and a mod_ssl dist for the reason
> that other module authors could use EAPI without mod_ssl, but not for the
> reason you mention IMHO. Actually the rebuilding of DSOs should be no longer
> needed, because Apache+EAPI since mod_ssl 2.2.0 can also load standard DSOs.
> And OTOH for the "have to dists" issue: You have an EAPI distribution. It's
> the same as the mod_ssl distribution but you use --with-eapi-only on the
> configure command line. This way only EAPI is applied to the Apache source
> tree. Isn't that what you actually want?
Looks like you miss his point. It's NOT about OTHER DSO's but about mod_ssl
itself. If EAPI and mod_ssl will be separated then with new version of mod_ssl
you'll need just recompilation of mod_ssl via apxs but when EAPI is changed
you should recompile Apache itself !
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
