On Sun, 31 Oct 2010 16:51:13 +0100, Mehdi Dogguy wrote: > > Without this package, BTI and other twitter clients will not function in > > squeeze, as they would not be able > > to authenticate with Twitter. > While this appears to be useful for Twitter clients (those actually > using the lib), there is not a single application build-depending on > this library for now. So, why should we accept this in Squeeze?
JFTR: bti would already (build-)depend on it if it had been around longer :) (In fact I have a package ready with the new upstream release of bti which uses liboauth). > > libOAuth was accepted very recently into Debian Unstable, and that > > is why it isn't in squeeze yet. > Then, we won't be able to accept it in Squeeze I'm afraid. Right, that's totally understandable. I guess this is one of the cornercases where we have to sacrifice an improvement in a small corner in order to improve the larger good (i.e. get out the release without unnecessary delays and risk for the quality). (And we can then upload a newer bti + liboauth + other clients into backports.) Cheers, gregor -- .''`. http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4 : :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe `- BOFH excuse #244: Your cat tried to eat the mouse.
signature.asc
Description: Digital signature
