Changes: version 2.1.0 (07/28/2007): libpurple: * Core changes to allow UIs to use second-granularity for scheduling. Pidgin and Finch, which use the glib event loop, were changed to use g_timeout_add_seconds() on glib >= 2.14 when possible. This allows glib to better group our longer timers to increase power efficiency. (Arjan van de Ven with Intel Corporation) * No longer linkifies screennames containing @ signs in join/part notifications in chats * With the HTML logger, images in conversations are now saved. NOTE: Saved images are not yet displayed when loading logs. * Added support for QIP logs to the Log Reader plugin (Michael Shkutkov) Pidgin: * Ensure only one copy of Pidgin is running with a given configuration directory. The net effect of this is that trying to start Pidgin a second time will raise the buddy list. (Gabriel Schulhof) * Undo capability in the conversation window * The formatting toolbar has been reorganized to be more concise. * A new status area has been added to the top of conversations to provide additional detail about the buddy, including buddy icon, protocol and status message. * Show idle times in the buddy list as days, hours, seconds Finch: * There's support for workspaces now (details in the manpage) * There's a new custom window manager, Irssi * Some improvements for tab-completion, tooltip and the password entries * Some bugs regarding search results fixed * A new DBus-script to create a docklet for finch * Support for showing empty groups in the buddy list (Eric Polino)
Created attachment 126576 [details] pidgin 2.1.0 ebuild package
Created attachment 126578 [details] pidgin 2.1.0 ebuild
ebuild attached works fine here, might want to change the line: # $Header: /var/cvsroot/gentoo-x86/net-im/pidgin/pidgin-2.0.2.ebuild,v 1.4 2007/07/20 21:48:53 tester Exp $ to indicate 2.1.0 instead of 2.0.2
The header should actually be cleared, but if its committed to portage it will be updated automatically There could be a problem with this ebuild a mono, I enabled the mono keyword but if you look in the about dialog in pidgin then it says that mono support has been diabled! I dont use any mono apps and its only on my system because some gnome thing use it! So I have no knowledge to look into that problem!
Ebuild works fine here too. Changing the $Header$ isn't needed, CVS will do so automatically. Also, Mono support is disabled on my set-up as well. Don't know what the option is supposed to do though.
(In reply to comment #5) > Also, Mono support is disabled on my set-up as well. Don't know what the option > is supposed to do though. That is, I use Mono on my system but Pidgin says it's disabled as well, even though the USE-flag is set.
the mono option allows writing plugins using mono.. its disabled because it causes pidgin to crash too much. And since I don't know any useful plugin written with mono..
I have spend a few hours on IRC, and many people tell about broken features when upgrading from 2.0.1 to 2.1.0 ... I was coming here to also report the version bump, but, before introducing it to portage, you should test if it is really stable enough. Just migrated from gaim 2.0beta6, and pidgin 2.0.2 works fine for me (using it since 45mn ).
I've been using it for a couple of days... no problems so far. However, I don't use any of the external plugins and almost none of the internal ones.
The ebuild already advices the user to backup his ~/.gaim/ (which is ~/.purple/ now, BTW), so I think that if there are problems they will be found and fixed much faster if it gets into portage. After all, this is the meaning of the unstable tree..
I've been using gaim 2.00 beta 6, Pidgin 2.00, 2.01, 2,02 found nothing broken. Ive now been using 2.10 since release still finding nothing broken. The only plugin I use is the OTR one. http://bugs.gentoo.org/187573 which is awaiting version bump. I'm only using these flags. + + crypt : Add support for encryption -- using mcrypt or gpg where applicable + + dbus : Enable dbus support for anything that needs it (gpsd, gnomemeeting, etc) + + gnutls : Adds support for net-libs/gnutls + + gtk : Adds support for x11-libs/gtk+ (The GIMP Toolkit) + + ncurses : Adds ncurses support (console display library) + + nls : Adds Native Language Support (using gettext - GNU locale utilities) + + perl : Adds support/bindings for the Perl language. + + spell : Adds dictionary support + + startup-notification : Enable application startup event feedback mechanism + + xscreensaver : Adds support for XScreenSaver extension.
It sounds like there's enough positive response to include this into portage as unstable testing. Is there a reason not to? ---Alex
devs being busy is the reason.. I'll try to do it tonight, but no guarantees..
I've been using 2.1.0 since it was released and have had no problems with it. Please include this in the tree.
I did not say migration is dangerous, but, warning you that some people had already found some bugs. All softwares are anyway release even when they have bugs ... what I have heard about is just about minor features anyway.
this is in tree.. sorry for the delay...
