This is the mail archive of the
mailing list for the Cygwin project.
Re: New packge: lighttpd-1.3.0
- From: "Gerrit P. Haase" <gp at familiehaase dot de>
- To: robin-lists at robinbowes dot com
- Cc: "'Reini Urban'" <rurban at x-ray dot at>, cygwin at cygwin dot com
- Date: Wed, 22 Sep 2004 12:30:57 +0200
- Subject: Re: New packge: lighttpd-1.3.0
- Organization: Esse keine toten Tiere
- References: <4150D148.firstname.lastname@example.org>
- Reply-to: "Gerrit @ cygwin" <cygwin at cygwin dot com>
> I think what is required is a separate php package - making it work
> with a web server (apache or lighttpd) is just a configuration
Yes, but you cannot build PHP with fastcgi and Apache support at the
same time, so there should be several packages, runtime for every
webserver available (currently only lighttpd) plus one common
package (devel stuff).
> I imagine most of the problems arise when trying to decide on a
> standard set of modules to be included with the "standard" php
> package. Or is it possible to package php modules separately, e.g.
> the postgres, ssl, imap, etc.?
Just include everything possible seems to be ok;) There should be all
important modules which are really needed, e.g. database modules for
mysql and pgsql, sqlite and others, all graphic stuff possible (GD,
JPEG, PNG, ...), cryptographic stuff like openssl, mhash, ...,
compression, pear, XML/XSLT, pdflib, PSPELL? Well you see, one cannot
say which extension is important and which isn't, just try to use
every available extension seems to be ok IMO.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html