On Thu, Jan 17, 2008 at 09:51:45PM +0000, Ilya M. Slepnev wrote: > [EMAIL PROTECTED] > On 1/17/08, Pierre Habouzit <[EMAIL PROTECTED]> wrote: > > On Thu, Jan 17, 2008 at 08:07:22PM +0000, Pierre Habouzit wrote: > > > Please just don't sponsor this upload. lighttpd is nowhere near > > > production quality, and debian won't upload it. I don't know why I > > > overlooked this bug report, it seems my procmail filter needs serious > > > tweaking, but (1) there is absolutely no valid reasons to have 2 > > > separate lighttpd packages and (2) the 1.5 version is not stable enough. > > > > Okay, I god confused with lighttpd 2.0, 1.5 is just the next in line > > in the same generation as 1.4.18 (currently in debian), and 1.5 is _NOT_ > > released yet. So packaging it is nonsense. > > > > I'm closing the bug, we don't package unreleased software, we only > > backport patches if needed. > > Even in experimental?
One could package it in experimental indeed, though no-one will upload rogue packages like yours. If you are interested in maintaining lighttpd, please join the team, do not work behind its back. > Why are your talking about nonsense of packaging? Beacuse it seems all but stable, and packaging unstable APIs or programs is a hell I'm not keen on trying. > It has sense. Can you really imagine a process of backporting modules > from 1.5 to 1.4? And by the greatest luck, there is no 1.5 modules in debian right now, so I believe we're safe for now. > I can cite lighttd.net: > "If you are developing a plugin for 1.4.x right now, be asured that it > won't work without changes in 1.5.0." Well, then develop it for 1.5.0 if you don't care about 1.4.x, so build yourself a development environment on your computer with the latest bleeding-edge svn snapshot, bless you. Be sure that lighttpd 1.5 will enter unstable as soon as it's released and of release quality. -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgp7YR5jZHmsA.pgp
Description: PGP signature
