libsecret: New package
PATCH v2 1/1 libsecret: New package
libsecret is a library for storing and retrieving passwords and other secrets. It communicates with the "Secret Service" using DBus. gnome-keyring and ksecretservice are both implementations of a Secret Service.
libsecret replaces libgnome-keyring.
https://wiki.gnome.org/Libsecret
---
Changes since v1:
- depend on USE_WCHAR and TOOLCHAIN_HAS_THREADS which are required by libglib2
http://lists.busybox.net/pipermail/buildroot/2013-August/076565.html
--- package/Config.in | 1 + package/libsecret/Config.in | 25 +++++++++++++++++++++++++ package/libsecret/libsecret.mk | 24 ++++++++++++++++++++++++ 3 files changed, 50 insertions(+) create mode 100644 package/libsecret/Config.in create mode 100644 package/libsecret/libsecret.mk
package/Config.in +1 -0
@@ -423,6 +423,7 @@ source "package/libassuan/Config.in" source "package/libmcrypt/Config.in" source "package/libmhash/Config.in" source "package/libnss/Config.in" +source "package/libsecret/Config.in" source "package/libsha1/Config.in" source "package/nettle/Config.in" source "package/openssl/Config.in"
package/libsecret/Config.in new file +25 -0
@@ -0,0 +1,25 @@ +config BR2_PACKAGE_LIBSECRET + bool "libsecret" + select BR2_PACKAGE_LIBGLIB2 + depends on BR2_USE_WCHAR # gettext dep in libglib2 + depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2 + help + libsecret is a library for storing and retrieving passwords and other + secrets. It communicates with the "Secret Service" using DBus. + gnome-keyring and ksecretservice are both implementations of a Secret + Service. + + https://wiki.gnome.org/Libsecret + +comment "libsecret requires a toolchain with WCHAR and threading support." + depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS + +if BR2_PACKAGE_LIBSECRET + +config BR2_PACKAGE_LIBSECRET_CRYPTO + bool "Enable gcrypt and transport encryption" + select BR2_PACKAGE_LIBGCRYPT + help + Enable gcrypt and transport encryption + +endif
package/libsecret/libsecret.mk new file +24 -0
@@ -0,0 +1,24 @@ +################################################################################ +# +# libsecret +# +################################################################################ + +LIBSECRET_VERSION = 0.15 +LIBSECRET_SITE = http://ftp.gnome.org/pub/GNOME/sources/libsecret/$(LIBSECRET_VERSION) +LIBSECRET_SOURCE = libsecret-$(LIBSECRET_VERSION).tar.xz +LIBSECRET_LICENSE = LGPLv2.1+ +LIBSECRET_LICENSE_FILES = COPYING +LIBSECRET_INSTALL_STAGING = YES + +LIBSECRET_DEPENDENCIES = libglib2 +LIBSECRET_CONF_OPT = --disable-manpages --disable-strict --disable-coverage --enable-vala=no + +ifeq ($(BR2_PACKAGE_LIBSECRET_CRYPTO),y) + LIBSECRET_DEPENDENCIES += libgcrypt + LIBSECRET_CONF_OPT += --enable-gcrypt +else + LIBSECRET_CONF_OPT += --disable-gcrypt +endif + +$(eval $(autotools-package))
Signature · 1 line
1.8.3.2
PATCH v2 1/1 libsecret: New package
Quoted 4 lines · Markos Chandras
libsecret is a library for storing and retrieving passwords and other secrets. It communicates with the "Secret Service" using DBus. gnome-keyring and ksecretservice are both implementations of a Secret Service.
I'm surprised it doesn't require dbus if it uses dbus for communicating
with the secret service...
Quoted 47 lines
libsecret replaces libgnome-keyring.
https://wiki.gnome.org/Libsecret
Signed-off-by Markos Chandras <[email protected]>---
Changes since v1:
- depend onUSE_WCHARandTOOLCHAIN_HAS_THREADSwhich are required by libglib2
http://lists.busybox.net/pipermail/buildroot/2013-August/076565.html--- package/Config.in | 1 + package/libsecret/Config.in | 25 +++++++++++++++++++++++++ package/libsecret/libsecret.mk | 24 ++++++++++++++++++++++++ 3 files changed, 50 insertions(+)create mode 100644 package/libsecret/Config.in create mode 100644
package/libsecret/libsecret.mkpackage/Config.in +1
-0@@ -423,6 +423,7 @@ source "package/libassuan/Config.in" source "package/libmcrypt/Config.in" source "package/libmhash/Config.in" source "package/libnss/Config.in" +source "package/libsecret/Config.in" source "package/libsha1/Config.in" source "package/nettle/Config.in" source "package/openssl/Config.in"package/libsecret/Config.in new file +11
-0@@ -0,0 +1,25 @@ +config BR2_PACKAGE_LIBSECRET + bool "libsecret" + select BR2_PACKAGE_LIBGLIB2 + depends on BR2_USE_WCHAR # gettext dep in libglib2 + depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2 + help + libsecret is a library for storing and retrieving passwords and other + secrets. It communicates with the "Secret Service" using DBus. + gnome-keyring and ksecretservice are both implementations of a Secret + Service. +
package/libsecret/Config.in line 21
Quoted 10 lines
package/libsecret/Config.in new file +10
-0+ https://wiki.gnome.org/Libsecret + +comment "libsecret requires a toolchain with WCHAR and threading support." + depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS + +if BR2_PACKAGE_LIBSECRET + +config BR2_PACKAGE_LIBSECRET_CRYPTO + bool "Enable gcrypt and transport encryption" + select BR2_PACKAGE_LIBGCRYPT
Does the gcrypt support make a major difference for library size or
compilation time? Otherwise, we usually include it automatically if libgcrypt is selected. I personally like to mention this in the help text in that case, i.e. something like
Select BR2_PACKAGE_LIBGCRYPT to enable transport encryption.
But basically looks good to me. Untested though.
Regards,
Arnout
Quoted 35 lines
package/libsecret/Config.in new file +4
-0+ help + Enable gcrypt and transport encryption + +endifpackage/libsecret/libsecret.mk new file +24
-0@@ -0,0 +1,24 @@ +################################################################################ +# +# libsecret +# +################################################################################ + +LIBSECRET_VERSION = 0.15 +LIBSECRET_SITE = http://ftp.gnome.org/pub/GNOME/sources/libsecret/$(LIBSECRET_VERSION) +LIBSECRET_SOURCE = libsecret-$(LIBSECRET_VERSION).tar.xz +LIBSECRET_LICENSE = LGPLv2.1+ +LIBSECRET_LICENSE_FILES = COPYING +LIBSECRET_INSTALL_STAGING = YES + +LIBSECRET_DEPENDENCIES = libglib2 +LIBSECRET_CONF_OPT = --disable-manpages --disable-strict --disable-coverage --enable-vala=no + +ifeq ($(BR2_PACKAGE_LIBSECRET_CRYPTO),y) + LIBSECRET_DEPENDENCIES += libgcrypt + LIBSECRET_CONF_OPT += --enable-gcrypt +else + LIBSECRET_CONF_OPT += --disable-gcrypt +endif + +$(eval $(autotools-package))
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
PATCH v2 1/1 libsecret: New package
Hi Arnout,
Quoted 8 lines · Arnout Vandecappelle
Does the gcrypt support make a major difference for library size or
compilation time? Otherwise, we usually include it automatically if libgcrypt is selected. I personally like to mention this in the help text in that case, i.e. something likeSelect
BR2_PACKAGE_LIBGCRYPTto enable transport encryption.
It does not make huge difference neither in compilation time nor in file size
The libsecret library with the gcrypt support is about 100K bigger in size
I don't mind submitting a new patch removing the BR2_PACKAGE_LIBSECRET_CRYPTO option.
I sent this patch before seeing your comments on the harfbuzz patch I sent :)
Quoted 7 lines
But basically looks good to me. Untested though.
Thank you!
Signature · 2 lines
Regards, Markos Chandras