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
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
Message-ID: <49284.66.32.89.136.1019089982.squirrel@secure2.ece.gatech.edu>
Date: Wed, 17 Apr 2002 20:33:02 -0400 (EDT)
Subject: Re: extra apache shared module DLLs
To: <tolj AT wapme-systems DOT de>
In-Reply-To: <3CBDFF45.3748CE16@wapme-systems.de>
References: <3CBDFF45 DOT 3748CE16 AT wapme-systems DOT de>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Cc: <cygwin-apps AT cygwin DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)

> What about modules that do change/patch Apache's source tree to hook on
> certain structures that can not be accessed using the "normal" API?
>
> I'm thinking espacially about mod_ssl and mod_snmp, which both need to
> patch Apache's core to be applied?


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.

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.

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?

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

--Chuck