On Thu, Feb 04, 1999, Ronan-Yann Lorin wrote:
>[...]
> If we have an eapi-x.x.tar.gz we know that we have to rebuild Apache when it
> becomes eapi-x.y.tar.gz. On the other hand when mod_ssl's version changes
> we know that we only have to rebuild mod_ssl.
You talk about "knowledge", but that's just a matter of remembering the stuff.
So, as I said, seems like the concern is more related to a nice named tarball
for EAPI than technically related. Hmmm.. the problem is that I then have to
maintain one more Apache-related package. I'm not convinced it is worth
the overhead. Hmmm...
> Do I understand that the eapi is now compatible with standard api and an
> Apache+EAPI can run a standard Apache module?
It always was able to run a standard Apache module without changes, of course.
What you talk about is a DSO _binary_ of a standard Apache module. Yes, with
the latest version of EAPI you can load both DSOs which were aware of EAPI at
compile-time _and_ modules compiled with plain Apache's.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
