Message-Id: <200409220125.i8M1P7Fs000485@delorie.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: <robin-lists@robinbowes.com>
To: "'Reini Urban'" <rurban@x-ray.at>
Cc: <cygwin@cygwin.com>
Subject: RE: New packge: lighttpd-1.3.0
Date: Wed, 22 Sep 2004 02:25:07 +0100
Organization: robinbowes.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <4150D148.2000600@x-ray.at>

> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Reini Urban
> Sent: 22 September 2004 01:12
> Cc: cygwin@cygwin.com
> Subject: Re: New packge: lighttpd-1.3.0
> 
> >>But why wait for me?  Try it yourself?  No problem that
> >>cannot be discussed at this list (as long as it is about 
> problems with
> >>building some open sourced code for cygwin).
> 
> robin schrieb:
> > Not sure where to go with this now - I'll try setting up a 
> php application that
> > uses a database or something.
> > 
> > Any suggestions?
> 
> Either make Jan adding php and fastcgi support by himself,
> or ITP a lighttpd-php package at apps.

I think what is required is a separate php package - making it work with a web
server (apache or lighttpd) is just a configuration issue.

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.?

R.
--
http://robinbowes.com  


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/