Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3CBE9930.FED8AA3E@wapme-systems.de>
Date: Thu, 18 Apr 2002 12:00:16 +0200
From: Stipe Tolj <tolj AT wapme-systems DOT de>
Organization: Wapme Systems AG
X-Accept-Language: de
MIME-Version: 1.0
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: extra apache shared module DLLs
References: <3CBDFF45 DOT 3748CE16 AT wapme-systems DOT de> <49284 DOT 66 DOT 32 DOT 89 DOT 136 DOT 1019089982 DOT squirrel AT secure2 DOT ece DOT gatech DOT edu>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Charles Wilson wrote:
> 
> Well, you can run an mod_ssl-modified apache without having the mod_ssl
> stuff "on".  (e.g. the .conf file doesn't load_module it).  I'd assume that
> the same is true for mod_snmp.  So, I'd distribute the core apache package
> with those modifications -- but without the modules (mod_ssl.dll)
> themselves, and with the corresponding load_module statements commented out
> of the .conf.

yep, but you still have a patched core. In case of mod_ssl, Ralf is
adding the EAPI structures to the core. Even if you don't use the
mod_ssl module, the core is still modified, so this can not be
considered as an "official" port. 

> Then, the user could install the mod_ssl package, which would install the
> module .dll and related stuff, have a postinstall script to generate some
> dummy, self-signed server keys, and create an includable ssl-conf file.
> 
> It would still be up to the user to add "include mod_ssl.conf" and uncomment
> the load_module statement in the main apache conf file.
> 
> Similar for mod_snmp.

hmmm, yeah, that should be a practible way I guess.

> Now, MOST modules don't require intrusive changes to the core apache.  So
> most mod_ packages don't need this special treatment.  BUT, of those modules
> that DO require it, which ones should you, Stipe, include pre-modified in
> the main apache package?

yep, I know. But mod_ssl is definitly one of the most important
modules, so that's why I raised the question.

> The ones you as maintainer FEEL like including.  I gather that means mod_ssl
> and mod_snmp, right now. :-)

yep, those should go in, even while mod_snmp is yet not compiling on
Cygwin and I'm having this on my TODO list.

We may gather a module list that may be suiteable for Cygwin from
other Linux distros like RedHat, SuSE, etc?!

Stipe

tolj AT wapme-systems DOT de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info AT wapme-systems DOT de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are