Bug#782448: ITP: telepathy-gabble-legacy -- Jabber/XMPP connection manager (legacy branch)
On 12/04/15 12:51, Jonas Smedegaard wrote: * Package name: telepathy-gabble-legacy ... NB! This is an older legacy branch of Gabble with Tubes API, requires for use with Sugar. If you do not need Tubes API then you are strongly recommended to instead use the regular telepathy-gabble package. I consider the (re-)addition of this package to be unwise. The Tubes channel type was deprecated in favour of the StreamTube and DBusTube channel types in May 2009. Depending how you count, it was removed from Gabble more than 3 years later (development version 0.17.1) or more than 4 years later (stable version 0.18.0); it's not as if this was some sudden flag-day transition. The reason for deprecation was that Tubes channels are not usable by telepathy-mission-control, or particularly meaningful at all: the sensible unit for dispatching is an individual tube within the channel. sugar-presence-service does essentially the same things as Mission Control, so having it dispatch singular Tube channels to applications (either directly or by using Mission Control) would probably be a considerable simplification. The packaging will be maintained by the Debian Sugar Team - unless the Debian Telepathy maintainers is willing to take over (hence Cc'ed) :-) I am not a member of the Telepathy team any more, either upstream or in Debian, but I was at the time this version was released. I would recommend that neither they nor you should keep this branch on life-support. S -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/552d03a8.6090...@debian.org
Bug#782448: ITP: telepathy-gabble-legacy -- Jabber/XMPP connection manager (legacy branch)
Hi Simon, Quoting Simon McVittie (2015-04-14 14:10:16) On 12/04/15 12:51, Jonas Smedegaard wrote: * Package name: telepathy-gabble-legacy ... NB! This is an older legacy branch of Gabble with Tubes API, requires for use with Sugar. If you do not need Tubes API then you are strongly recommended to instead use the regular telepathy-gabble package. I consider the (re-)addition of this package to be unwise. The Tubes channel type was deprecated in favour of the StreamTube and DBusTube channel types in May 2009. Depending how you count, it was removed from Gabble more than 3 years later (development version 0.17.1) or more than 4 years later (stable version 0.18.0); it's not as if this was some sudden flag-day transition. The reason for deprecation was that Tubes channels are not usable by telepathy-mission-control, or particularly meaningful at all: the sensible unit for dispatching is an individual tube within the channel. sugar-presence-service does essentially the same things as Mission Control, so having it dispatch singular Tube channels to applications (either directly or by using Mission Control) would probably be a considerable simplification. The packaging will be maintained by the Debian Sugar Team - unless the Debian Telepathy maintainers is willing to take over (hence Cc'ed) :-) I am not a member of the Telepathy team any more, either upstream or in Debian, but I was at the time this version was released. I would recommend that neither they nor you should keep this branch on life-support. Thanks a lot for your input, it is highly appreciated! It is my clear impression that Sugar developers intend to migrate to the new Tubes API (or, as you clarify: StreamTube and DBusTube). I am unaware why they didn't do so long ago - the little I discussed it with then it seems there is not even a process to migrate yet, so I fear it will take time to get that in place. I will bring your information to their attention, and take your strong advice _against_ keeping the old Tubes API alive into consideration. That said, it is my concrete experience that Sugar with old Tubes works, and Sugar with newer Telepathy Gabble does not work right now - and there are several opportunities in the relative short-term for active deployments to shift from Fedora-based Sugar to Debian-based. Obviously only if we can provide a fully working Sugar, so unless it is outright danegrous to use, I might end up packaging telepathy-gabble-legacy despite your advice, for use until Sugar developers get their act together. Regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#782448: ITP: telepathy-gabble-legacy -- Jabber/XMPP connection manager (legacy branch)
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard d...@jones.dk -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: telepathy-gabble-legacy Version : 0.16.7 Upstream Author : Collabora Ltd. * URL : http://telepathy.freedesktop.org/wiki/ * License : LGPL-2.1+ Programming Lang: C Description : Jabber/XMPP connection manager (legacy branch) Gabble is a Jabber/XMPP connection manager for the Telepathy framework, currently supporting single user chats, multi user chats and voice/video calls. Install this package to use Telepathy instant messaging clients with Jabber/XMPP servers, including Google Talk and Facebook Chat. . NB! This is an older legacy branch of Gabble with Tubes API, requires for use with Sugar. If you do not need Tubes API then you are strongly recommended to instead use the regular telepathy-gabble package. This package is needed by (all branches of) Sugar, which rely on the Tubes API no longer provided by mainline telepathy-gabble. The packaging will be maintained by the Debian Sugar Team - unless the Debian Telepathy maintainers is willing to take over (hence Cc'ed) :-) - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVKlxAAAoJECx8MUbBoAEhyrcP/jU5vPwPGHtbM2na+PdFmwgr Wbz6HZQqmcObnBljbtZbjKB7wbnJh5Gc7AljwEuDpeRPbFNnIhrS+gkedV4+bNCM wYzuE8AClLy5NViZP4Jl3YheUx+yKf7CkpC0KzHBqjldjz2AFTlKpo2zzpE9I8ML GjoRFnwC6S5vtywXkgq/CFB7MbiO+epzixbWJAufduEYaSj7R5pdvnvjl3WGdFMR 1OfKx6JZzT1PH/i07MzBBDlQhWBSgIqU+Y6ZV33OHvlsGtdAABKMC+FqHQUsswgy r5HxJMpQQ7HbjcTzYHXVoA5QEY2IiMtiR46kWUp2O+iuYmoso9M/yK4POz5oyLcM nuJJbD8d/naWwRhq69AtIhDzfE0tzi9Oz4k7e8obUS2LyRKdNg8jqJVo6BlyEti2 co7LAV7r7w4WKZFULKdN0pjbaxtB1H/SV7L/qpIkYXQKpdjm0hI0LQD+0Pv5iKPg 56JP7sHcwCOyUIr3DqpFR90+kVuHvjgFRWaiUBlD9nmNRGb8JpJnt55+fdR/Prji 8BAdSSzil+wHgwmixruSbkzXJ9b/PWKobkZ+0yN8DrnyarnY8WEuhZ2oy/YY3z32 xwnt8QLUoN76bmA3lq2ZqHdAejoE99xClaWjrHK37Ivy2S3UO6GAdlE5XwOiARuO bULMN54QI0x7XL7HC+JE =bo68 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150412115131.30463.23539.report...@bastian.jones.dk
