From 5dbf66ed84bc44ff44a2471355601f619087cafb Mon Sep 17 00:00:00 2001 From: dequis Date: Sun, 12 Jun 2016 21:55:26 -0300 Subject: purple: add $plugindir/purple to the plugin search path This allows adding bitlbee-specific purple plugins in a directory controlled by the user who starts bitlbee (as it can be defined in bitlbee.conf, PluginDir). Pidgin and finch have something similar allowing users to place plugins in ~/.purple/plugins: path = g_build_filename(purple_user_dir(), "plugins", NULL); The direct equivalent would be to use our config dir, but i'd rather not put executable modules there. --- protocols/purple/purple.c | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'protocols') diff --git a/protocols/purple/purple.c b/protocols/purple/purple.c index 6ea2d7d8..db553407 100644 --- a/protocols/purple/purple.c +++ b/protocols/purple/purple.c @@ -1453,6 +1453,10 @@ void purple_initmodule() purple_util_set_user_dir(dir); g_free(dir); + dir = g_strdup_printf("%s/purple", global.conf->plugindir); + purple_plugins_add_search_path(dir); + g_free(dir); + purple_debug_set_enabled(FALSE); purple_core_set_ui_ops(&bee_core_uiops); purple_eventloop_set_ui_ops(&glib_eventloops); -- cgit v1.2.3