diff options
| author | dequis <dx@dxzone.com.ar> | 2016-06-12 21:55:26 -0300 |
|---|---|---|
| committer | dequis <dx@dxzone.com.ar> | 2016-06-12 21:55:26 -0300 |
| commit | 5dbf66ed84bc44ff44a2471355601f619087cafb (patch) | |
| tree | bd3fa89e3f6ebb99cd95e9d1c1893395143a3862 | |
| parent | 135271c12dda487556a7e36fb7f3256a2d2e3c90 (diff) | |
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.
| -rw-r--r-- | protocols/purple/purple.c | 4 |
1 files changed, 4 insertions, 0 deletions
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); |