Gabber 2 is the next generation of Gabber: The Gnome Jabber Client. Gabber 2 is a Jabber client written in C++ using Gtkmm2 which is currently available for Linux and Mac OS X (under X11). Gabber is a Free and Open Source GNOME client for an instant messaging system called Jabber. Jabber is a Free and Open Source distributed instant messaging system. It does not rely on a single server, and the protocol is well documented. Jabber allows communication with many different instant messaging systems, including ICQ and AIM. There are several different Jabber clients already, but no other GNOME clients as of this writing. Hopefully Gabber will serve the purpose of being a robust GNOME Jabber client well. See attached ebuild.
Created attachment 28028 [details] An ebuild file for gabber-1.9.3 package
Gabber needs jabberoo library, ebuild for which I have already submitted, I'm adding a bug dependency.
bug-wranglers, please re-assign this to someone interested in maintaining net-im.
I am testing this and am having problems with configure not detecting the Xscreensaver extension. Also i have no idea how to change the auto-speel no a non english languague, but that is probabaly a gabber problem. I will be adding this and jabberoo to portage.
Works for me: checking for XScreenSaverRegister in -lXext... no checking for XScreenSaverRegister in -lXss... yes ..and then: Configuration: Install path: /usr Debugging symbols: no Enable OpenSSL support: yes GtkSpell spell checking: no XScreenSaver Extension: yes
Created attachment 28243 [details] gabber-1.9.3.ebuild This ebuild try's to use the Gnome2.eclass functions. But i am having problems. This is probably some problem in the configure script. I tried running it by hand i got this: If i run with --enable-ssl at the end of configure i get a message about no ssl. If i run witought --enable-ssl i have ssl. The same for GtkSpell and the Xss. Only works for debug.
that is because the configure script is broken, it defaults to disabling the switches no matter what --{dis,en}able-xxx is given. The only correct switch seems to be the debug one.
Right now i am in class I will make today a version of the ebuild that cheks for no ssl and spell flags and in that case adds the --disable, and if the flags are there will not touch them :) Also filling a bug upstream might be a good idea, can you do that foser as you seem to be in contact with the gabber2 people or do you want me to do that?
I wonder why does it work for me then.. see my previous comment
I am uploading a new version to CVS now. Andrej Kacian: Yes it does because in your ebuild nothing is passed to the configure script if the flag is activated.
*** Bug 45581 has been marked as a duplicate of this bug. ***
works for me, though I found this new re-write of gabber still lacking in some important functionality -like registering a new account with a server.
not much surprising considering it's a development release. humpback : if we fix the configure stuff instead of working around it, we help upstream development and ourselves for future releases.
*** Bug 40250 has been marked as a duplicate of this bug. ***
The latest version in portage is 1.9.4. This is going to be hardmasked until some problems get fixed in upstream (i contacted the author and he promised me a fix by 1.9.5) Thanks to all that participated here.
