On Sun, May 22, 2005 at 09:40:46PM +0200, Adeodato Simó wrote: > Short summary: upstream releaases of libgadu return their > gg_libgadu_version() in the MAJOR.MINOR.YYYYMMDD format. However, > now that cvs snapshots are in sid, the format has changed to YYYYMMDD.
What a mess :-( It's a lesson for me to really keep change sets minimal uploads such as the last one :-/ The problem seems to be that kopete gadu plugin author(s) assumed that what gg_libgadu_version returns actually means something in particular about the library capabilities. It doesn't, and this is libgadu's upstream's fault. And IIRC, they know it. I'll try to fix this situation for the long term, but it's not going to improve before sarge release. > As I understand it, the library should not change its behaviour > gratuitously, and should behave as the official upstream releases even > if it incorporates patches from CVS. Well, assuming that we have no time now to make both kopete and libgadu to do the Right Things about the version string, I guess that me patching libgadu's source to return 1.5.DATE is the best thing to do at present. I'll try to do that tommorow, together with applying some new fixes for variable signedness in ekg, which will probably turn out to be RC (I have no time today to investigate them thoroughly). Marcin PS: my Mutt+vim seem to have mangled your last name, sorry for that. -- Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
