diff options
Diffstat (limited to 'src/backends/gnome/configure-sub.in')
| -rw-r--r-- | src/backends/gnome/configure-sub.in | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/src/backends/gnome/configure-sub.in b/src/backends/gnome/configure-sub.in index 199989e8..d02d52a6 100644 --- a/src/backends/gnome/configure-sub.in +++ b/src/backends/gnome/configure-sub.in @@ -1,10 +1,13 @@ -PKG_CHECK_MODULES(KEYRING, [gnome-keyring-1 >= 2.20], HAVE_KEYRING=yes, HAVE_KEYRING=no) +# According to https://developer.gnome.org/libsecret/0.16/libsecret-Password-storage.html#secret-password-store-sync +# the simple API was still considered unstable. All supported distros +# now have 0.18 where the API is stable. +PKG_CHECK_MODULES(KEYRING, [libsecret-1 >= 0.18], HAVE_KEYRING=yes, HAVE_KEYRING=no) AC_ARG_ENABLE(gnome-keyring, AS_HELP_STRING([--enable-gnome-keyring], - [enables or disables support for the GNOME keyring; default is on if development files are available]), + [enables or disables support for the GNOME keyring via libsecret; default is on if development files are available]), [enable_gnome_keyring="$enableval" test "$enable_gnome_keyring" = "yes" || test "$enable_gnome_keyring" = "no" || AC_MSG_ERROR([invalid value for --enable-gnome-keyring: $enable_gnome_keyring]) - test "$enable_gnome_keyring" = "no" || test "$HAVE_KEYRING" = "yes" || AC_MSG_ERROR([gnome-keyring-1 pkg >= 2.20 not found, needed for --enable-gnome-keyring])], + test "$enable_gnome_keyring" = "no" || test "$HAVE_KEYRING" = "yes" || AC_MSG_ERROR([libsecret-1 >= 0.18 not found, needed for --enable-gnome-keyring])], enable_gnome_keyring="$HAVE_KEYRING") if test $enable_gnome_keyring = "yes"; then have_keyring=yes |