Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3CBB261A.6BB303CB@wapme-systems.de> Date: Mon, 15 Apr 2002 21:12:26 +0200 From: Stipe Tolj Organization: Wapme Systems AG X-Accept-Language: de,en MIME-Version: 1.0 To: cygwin-apps Subject: extra apache shared module DLLs Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Howdy, I'd like to hear from the list how we should distribute additional apache shared module DLLs that don't come with the Apache official source tree. I think especially of all the modules I had been doing for the CAMP (Cygwin Apache MySQL PHP Framework) like: mod_php4 mod_ssl mod_auth_mysql mod_auth_ntsec ... and so on. From my point of view we may have 3 alternatives: (i) package each module to an "apache-mod_foobar-X-Y.tar.bz2" binary package and distribute through the standard Cygwin setup.exe (setting setup.hint to require the apache-1.3.x base package) (ii) do not distribute additional modules at all via setup.exe. In that case I would offer the pre-compiled modules via http://apache.dev.wapme.net/ (iii) build a large (with lots of modules) CAMP binary package and distribute that one as setup.exe package Any comments or suggestions? 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