We did it. I’m proud to announce the completed set of transports on Schokokeks.org, including MSN, ICQ, AIM, GaduGadu (just to have the longer cock than Mabber) and Yahoo!.
Personally I switched over to Gajim, a Python-implemented Jabber-client which makes use of PyGTK and is the best solution for the GNOME-desktop if you want to have a real Jabber-client with neat features like service-discovery. A side effect is that currently most of my ICQ-contacts are listed as numbers, so you have to pardon me when I ask who you are.
I can’t deny myself to say the Jabber-packages in Gentoo are in a bad status, for example ejabberd 1.0, the software we’re using on Schokokeks.org for short, isn’t included, nevertheless it has been released for a long time and is ready for production use. Another issue are transports: to quote my colleague Jens Ohlig: »There are two types of transports: rotten and broken«. That’s generally true, but using the Python-implemented family of Jabber-transports (PyMSN-t, PyAIM-t, PyICQ-t) you can ease the pain in the ass. But hey, they are all not in Gentoo’s portage. Just an outdated version of PyMSN-t flies around there. An in the wild of the WWW there are some packages, which are much lower (can’t imagine) quality. Installing the files on strange places, creating strange init-scripts and so on. So I was forced to create my own ebuilds for ejabberd, pyaim-t (not checked in yet), pymsn-t, pyicq-t. They have some things but generally they are working quite fine and they are included –as usual – in BreakMyGentoo.
And another issue: there is net-im/jabber-base in portage, which provides jabberd’s basic-files like /var/log/jabber/, /etc/jabber and so on. That’s generally a good idea, but you are forced to reflect this in every fucking ebuild. And that’s not done. This pisses me off. I want to provide a Yahoo-transport to my users and – as there is no python-replacement – it’s necessary to use the rotten old C-implementation which is based on Gaim (you know, Gaim …) and depends on jabberd-1.4, which is the bad one and does not reflect jabber-base. So compiling end’s up in collision errors and I have to edit the ebuild. Another thing is the init-script of jabberd-1.4, which I don’t need, ’cause I want to run Yahoo-transport, not jabberd-1.4, but it marks itself as providing jabber-server, but as the init-script of ejabberd contains also the declaration for providing jabber-server it comes to conflict. Simple and ugly solution: remove the init-script of jabberd-1.4. But, as you see, that’s not really Gentoo’s fashion, is it?
At last: I want to enlighten the GaduGadu-conspiracy. The whole GaduGadu thing is a hoax or do you know anybody who uses this?
Filed on 27-02-2006, 19:07 under AIM, BreakMyGentoo, Ebuild, GaduGadu, Gentoo, ICQ, Jabber, Jabber-Transports, Linux, MSN, Portage, PyAIM-t, PyICQ-t, PyMSN-t, Technology, www & seven comments & no trackbacks