2756806f84
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
20 lines
728 B
JavaScript
20 lines
728 B
JavaScript
// -*- mode: js; js-indent-level: 4; indent-tabs-mode: nil -*-
|
|
|
|
/* The name of this package (not localized) */
|
|
var PACKAGE_NAME = '@PACKAGE_NAME@';
|
|
/* The version of this package */
|
|
var PACKAGE_VERSION = '@PACKAGE_VERSION@';
|
|
/* 1 if gnome-bluetooth is available, 0 otherwise */
|
|
var HAVE_BLUETOOTH = @HAVE_BLUETOOTH@;
|
|
/* 1 if networkmanager is available, 0 otherwise */
|
|
var HAVE_NETWORKMANAGER = @HAVE_NETWORKMANAGER@;
|
|
/* gettext package */
|
|
var GETTEXT_PACKAGE = '@GETTEXT_PACKAGE@';
|
|
/* locale dir */
|
|
var LOCALEDIR = '@datadir@/locale';
|
|
/* other standard directories */
|
|
var LIBEXECDIR = '@libexecdir@';
|
|
var PKGDATADIR = '@datadir@/@PACKAGE_NAME@';
|
|
/* g-i package versions */
|
|
var LIBMUTTER_API_VERSION = '@LIBMUTTER_API_VERSION@'
|