Loading plugins by default

Etan Reisner pidgin at unreliablesource.net
Thu Mar 26 14:13:51 EDT 2009

On Wed, Mar 25, 2009 at 10:13:09PM -0700, Ka-Hing Cheung wrote:
> On Thu, 2009-03-26 at 01:08 -0400, Shreevatsa R wrote:
> > What would be a good way to distribute Pidgin such that some plugins
> > are loaded by default?
> >
> > More context:
> > Albert Zeyer has made some modifications (#2629, #8448) so that Pidgin
> > can be distributed as a a single .app bundle:
> > http://sourceforge.net/projects/pidgin-macosx/
> > He chose to enable some plugins he viewed as useful, in such a way
> > that they get loaded by default each time Pidgin is started. This
> > means that the user's preferences (of which plugins to load) are
> > ignored, so I'm wondering if there is a better way to do this.
> >
> > I can think of a few things; which of the following would work?
> > 1. Just ship a default prefs.xml that loads those plugins. Does Pidgin
> > look for preferences in any "system location" other than
> > $USER/.purple/prefs.xml, where this could be put?
> /etc/purple/prefs.xml is the preferred way of doing it.
> -khc

Which only works for new pidgin users. pidgin doesn't read that file if
the user has a prefs.xml file of their own. Just as a point of


More information about the Devel mailing list