Look for web extensions in ~/.config/lariza/web_extensions

~/.local/share isn't really an appropriate place because it's meant to
contain "data", possibly written by the application.

Usually, lariza's web extensions (.so files) are not placed in your home
directory anyway. Instead, they are installed somewhere in /usr. The
home directory only contains symlinks. So, in a way, those symlinks can
be considered "configuration items". Hence, ~/.config is where they
should live.

diff --git a/CHANGES b/CHANGES
index 4c6f50fbf1f2e8076bc06d44006c0ef24f857148..21e8479a0a5b5e92d17742dfc30caa6dcae910cf 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,5 +1,9 @@
 Release history for lariza
 
+next
+  [Changed]
+  - Web extensions are now looked for in ~/.config/lariza/web_extensions.
+
 v16.06  2016-06-26
   [Fixed]
   - Gtk warnings.

diff --git a/browser.c b/browser.c
index e17479123770ebdf18219ea35639ea3ba8769878..1e1fdc627b84511f5dc971c3861f8ed24f4bb020 100644 (file)
--- a/browser.c
+++ b/browser.c
@@ -976,7 +976,7 @@ main(int argc, char **argv)
 
     if (!cooperative_instances || cooperative_alone)
     {
-        c = g_build_filename(g_get_user_data_dir(), __NAME__, "web_extensions",
+        c = g_build_filename(g_get_user_config_dir(), __NAME__, "web_extensions",
                              NULL);
         webkit_web_context_set_web_extensions_directory(
             webkit_web_context_get_default(), c