Re: lighttpd1.5
[...]
> 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.
Surely, i don't want to work behind your back! Please, calm down, I
tried to contact lighttpd team, but your "procmail filter needs
serious tweaking", so I'm glad, that i contacted you at last.
What do you mean, by calling a package "rogue"? Because of procmail
filters or it is very bad-done? I'm debian maintaner for more then
four years, so I wouldn't try to hijack a package or work behind your
back and I respect your team and work, which you are doing for
lighttpd and debian.
> > 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 works stable for several clusters for us, BTW.
> > 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.
Yes, that's the problem. Let's try that in experimental?
[...]
> 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.
OK, i understand, that it is impossible to enter for lighttpd 1.5 to
enter unstable, surely.
But what about experimental? I'm not a fanatic, for building
"bleeding-edge svn snapshot" in a development environment, and i'm not
trying to do your work. That's why I packaged 1.5 in separate package,
for nobody to be confused about upgrade from 1.4 to 1.5.
--
Ilya
Reply to: