Mercurial > pidgin.yaz
view doc/Makefile.am @ 27556:cbee8aecc90a
Free the buddy list data some more at shutdown and some deprecations.
I think these deprecations are reasonable. Basically, purple_blist_init
should create a PurpleBuddyList*, so each UI doesn't need to do that.
The UI data for the PurpleBuddyList is more tightly coupled with
the PurpleBuddyList and purple_blist_destroy is called in
purple_blist_uninit (and is fully cleaned up now).
As libpurple works currently, I believe it's not really possible to have
multiple PurpleBuddyLists around (blist.c relies on a single global
variable) and when it was discussed on the mailing list a few months ago,
nobody was using it as such.
Refs #9253 (going to milestone 3.0.0 it).
author | Paul Aurich <paul@darkrain42.org> |
---|---|
date | Sun, 12 Jul 2009 02:55:36 +0000 |
parents | 380e7149a777 |
children | 76a689608a83 |
line wrap: on
line source
man_MANS = if ENABLE_GTK man_MANS += pidgin.1 endif if ENABLE_GNT man_MANS += finch.1 endif EXTRA_DIST = \ C-HOWTO.dox \ PERL-HOWTO.dox \ SIGNAL-HOWTO.dox \ TCL-HOWTO.dox \ TracFooter.html \ TracHeader.html \ account-signals.dox \ blist-signals.dox \ certificate-signals.dox \ cipher-signals.dox \ connection-signals.dox \ conversation-signals.dox \ core-signals.dox \ dbus-server-signals.dox \ funniest_home_convos.txt \ finch.1.in \ gtkaccount-signals.dox \ gtkblist-signals.dox \ gtkconv-signals.dox \ gtklog-signals.dox \ gtkimhtml-signals.dox \ gtkrc-2.0 \ imgstore-signals.dox \ log-signals.dox \ notify-signals.dox \ pidgin.1.in \ plugin-i18n.dox \ plugin-ids.dox \ plugin-signals.dox \ savedstatus-signals.dox \ sound-signals.dox \ the_penguin.txt \ xfer-signals.dox