I assume that there is no change in the EAPI part, or is there?
(I'm asking this question because we previously patched apache.1.3.9 with
the EPAI from mod_ssl 2.4.5)
Thanks,
--Yan
On Fri, 5 Nov 1999, Ralf S. Engelschall wrote:
>
> Because of the availability of a very important bugfix, I imme
Hi! With the kind help from this list (Ralf in particular) I
have successfully built modssl as an Apache DSO. Now I need
to figure out the license stuff before I can deploy it.
Our use of modssl/openssl should fall in the category of
commercial use.
My first question is about the patents to be in
On Thu, 7 Oct 1999, Ralf S. Engelschall wrote:
> On Thu, Oct 07, 1999, Yan Zhang Chen wrote:
>
> > 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 Ap
Hi!
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 extend
On Tue, 5 Oct 1999, Ralf S. Engelschall wrote:
> On Tue, Oct 05, 1999, Yan Zhang Chen wrote:
>
> > Just curious: why including binary files like the "etc/patch.tar"
> > in the source tree?
>
> Where else would you place them? Everything of mod_ssl is in CVS
Just curious: why including binary files like the "etc/patch.tar"
in the source tree? How am I supposed to handle this when I import the
source into CVS; importing the binary or importing the untarred text
files (which means I'll have "modified" the distribution tree before
putting it into CVS, wh
On Mon, 4 Oct 1999, Ralf S. Engelschall wrote:
> On Mon, Oct 04, 1999, Yan Zhang Chen wrote:
>
> > I'm new; just read the FAQ and searched the past mail archive, but still
> > have this question: is it OK (feasible & advisable) to build the latest
> > mod_ssl
Hi all!
I'm new; just read the FAQ and searched the past mail archive, but still
have this question: is it OK (feasible & advisable) to build the latest
mod_ssl (2.4.5) with earlier versions of Apache (v.1.3.4 specifically)?
I do see there is a "--force" option in mod_ssl for such purpose.
Any ex
