On Thu, Oct 07, 1999, Yan Zhang Chen wrote:
> I'm struggling to determine the best way to organize our Apache-related
> package structures. Looks like this EAPI (that mod_ssl depends on) might
> be complicating the things. Your advice would be most appreciated.
>
> Some background info:
> We have several Apache-based packages. One of them extends Apache with
> our own module, the others involve different combinations of PHP stuff
> (MySQL,IMAP,GD etc). Now we're enabling this openssl/mod_ssl to all the packages.
>
> Before the existence of EAPI, I was thinking about building one single
> Apache core, then each individual module could be built separately
> (without referencing to Apache source tree) as DSO via apxs. This would look
> really neat in terms of maintenance. Can I still do this with the introduction
> of this EAPI? (mod_ssl INSTALL doesn't tell how to build mod_ssl separately
> without Apache source tree; is it possible?)
Just build your Apache with EAPI only (see mod_ssl's --with-eapi-only option)
and then proceed as you wanted, i.e. build all modules as DSOs (including
mod_ssl). See "Upgrading with APXS (EXPERTS ONLY)" in the mod_ssl INSTALL
documents for a few hints.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
