eb7533bbf1
libnm doesn't only search for plugins in the regular VPN plugin directory, but also in the legacy location and the directory pointed to by the NM_VPN_PLUGIN_DIR environment variable (if set). We don't monitor the additional directories, so it's possible for our cache to become outdated. Instead of trying to play catch-up with libnm's internals, do what nm-applet does and use the appropriate API to look up the plugin on each request. https://gitlab.gnome.org/GNOME/gnome-shell/issues/2386
16 lines
517 B
Meson
16 lines
517 B
Meson
jsconf = configuration_data()
|
|
jsconf.set('PACKAGE_NAME', meson.project_name())
|
|
jsconf.set('PACKAGE_VERSION', meson.project_version())
|
|
jsconf.set('GETTEXT_PACKAGE', meson.project_name())
|
|
jsconf.set('LIBMUTTER_API_VERSION', mutter_api_version)
|
|
jsconf.set10('HAVE_BLUETOOTH', bt_dep.found())
|
|
jsconf.set10('HAVE_NETWORKMANAGER', have_networkmanager)
|
|
jsconf.set('datadir', datadir)
|
|
jsconf.set('libexecdir', libexecdir)
|
|
|
|
config_js = configure_file(
|
|
input: 'config.js.in',
|
|
output: 'config.js',
|
|
configuration: jsconf
|
|
)
|