Pierre Habouzit dijo [Mon, May 05, 2008 at 03:44:15PM +0200]:
> > So given that it's really from Lighttpd, and that it's likely that future
> > version will come from Lighttpd as well, not cherokee, shouldn't we give
> > Lighttpd priority?
>
> Well so maybe I'll take gunnar's manual page then
Pierre Habouzit dijo [Mon, May 05, 2008 at 03:44:15PM +0200]:
> > So given that it's really from Lighttpd, and that it's likely that future
> > version will come from Lighttpd as well, not cherokee, shouldn't we give
> > Lighttpd priority?
>
> Well so maybe I'll take gunnar's manual page then
On Mon, May 05, 2008 at 10:44:54AM +, Alexander Turcic wrote:
> Pierre, I am certain that spawn-fcgi comes from the Lighttpd team. Also
> check out this source snippet from the cherokee:
>
> http://svn.cherokee-project.com/browser/cherokee/trunk/contrib/spawn-fcgi.c
>
> * File borrowed from
Pierre, I am certain that spawn-fcgi comes from the Lighttpd team. Also
check out this source snippet from the cherokee:
http://svn.cherokee-project.com/browser/cherokee/trunk/contrib/spawn-fcgi.c
* File borrowed from lighttpd. I have only cleaned up the headers
* inclusion mess. Its original l
On Mon, May 05, 2008 at 07:22:17AM +, Michael Ablassmeier wrote:
> Package: cherokee, lighttpd
> Severity: serious
> Justification: policy violation
>
> hi,
>
> both cherokee and lighttpd ship
> `/usr/share/man/man1/spawn-fcgi.1.gz'
> but do neither conflict, nor add a diversion, thus fail
5 matches
Mail list logo
