libgpgme: Take into account that gnupg and gnupg2 are mutual exclusive
PATCH 1/1 libgpgme: Take into account that gnupg and gnupg2 are mutual exclusive
Avoid that libgpgme can select the gnupg package although gnupg2 has been already selected. Both packages are mutual exclusive and shouldn't be selected at the same time.
--- package/libgpgme/Config.in | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
package/libgpgme/Config.in +1 -1
@@ -2,7 +2,7 @@ config BR2_PACKAGE_LIBGPGME bool "libgpgme" depends on BR2_USE_MMU # libassuan #gnupg is not needed to build, but at runtime. - select BR2_PACKAGE_GNUPG + select BR2_PACKAGE_GNUPG if !BR2_PACKAGE_GNUPG2 select BR2_PACKAGE_LIBGPG_ERROR select BR2_PACKAGE_LIBASSUAN help
Signature · 1 line
1.7.1
PATCH 1/1 libgpgme: Take into account that gnupg and gnupg2 are mutual exclusive
Quoted 16 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Vicente" == Vicente Olivert Riera <[email protected]> writes:
Avoid that libgpgme can select the gnupg package although gnupg2 has been already selected. Both packages are mutual exclusive and shouldn't be selected at the same time.
Signed-off-by Vicente Olivert Riera <[email protected]>--- package/libgpgme/Config.in | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)package/libgpgme/Config.in +0
-0
package/libgpgme/Config.in config BR2_PACKAGE_LIBGPGME · line 5
Quoted 5 lines
package/libgpgme/Config.in +1
-1@@ -2,7 +2,7 @@ config BR2_PACKAGE_LIBGPGME bool "libgpgme" depends on BR2_USE_MMU # libassuan #gnupg is not needed to build, but at runtime. - select BR2_PACKAGE_GNUPG + select BR2_PACKAGE_GNUPG if !BR2_PACKAGE_GNUPG2
Committed, thanks.
I'm not familiar with libgpgme. Does it need to be configured somehow to use gpg2 instead of gpg? Would it make sense to automatically configure this if BR2_PACKAGE_GNUPG2 is enabled?
Signature · 1 line
Bye, Peter Korsgaard