diff options
author | Peter Hofmann <scm@uninformativ.de> | 2016-07-30 08:24:52 +0200 |
---|---|---|
committer | Peter Hofmann <scm@uninformativ.de> | 2016-07-30 08:24:52 +0200 |
commit | 82f095cdca849faca962fdb6ed65844ab0410166 (patch) | |
tree | 32ebe5b47bf1c820175cadbf317c478dc3e58ed8 | |
parent | 4c84c2c04e5d7d77155ed8c32c481c1e0053e96a (diff) | |
download | lariza-82f095cdca849faca962fdb6ed65844ab0410166.tar.gz |
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.
-rw-r--r-- | CHANGES | 4 | ||||
-rw-r--r-- | browser.c | 2 |
2 files changed, 5 insertions, 1 deletions
@@ -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. @@ -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 |