package/python-gnupg: new package
PATCH 1/1 package/python-gnupg: new package
A wrapper for the Gnu Privacy Guard (GPG or GnuPG).
The gnupg module allows Python programs to make use of the functionality provided by the GNU Privacy Guard (abbreviated GPG or GnuPG). Using this module, Python programs can encrypt and decrypt data, digitally sign documents and verify digital signatures, manage (generate, list and delete) encryption keys, using Public Key Infrastructure (PKI) encryption technology based on OpenPGP.
https://docs.red-dove.com/python-gnupg/
--- DEVELOPERS | 1 + package/Config.in | 1 + package/python-gnupg/Config.in | 15 +++++++++++++++ package/python-gnupg/python-gnupg.hash | 5 +++++ package/python-gnupg/python-gnupg.mk | 13 +++++++++++++ 5 files changed, 35 insertions(+) create mode 100644 package/python-gnupg/Config.in create mode 100644 package/python-gnupg/python-gnupg.hash create mode 100644 package/python-gnupg/python-gnupg.mk
DEVELOPERS +1 -0
@@ -1595,6 +1595,7 @@ F: package/fluidsynth/ F: package/glslsandbox-player/ F: package/ptm2human/ F: package/python-distro/ +F: package/python-gnupg/ F: package/python-pyalsa/ N: Julien Viard de Galbert <[email protected]>
package/Config.in +1 -0
@@ -1038,6 +1038,7 @@ menu "External python modules" source "package/python-futures/Config.in" source "package/python-git/Config.in" source "package/python-gitdb2/Config.in" + source "package/python-gnupg/Config.in" source "package/python-gobject/Config.in" source "package/python-gpiozero/Config.in" source "package/python-greenlet/Config.in"
package/python-gnupg/Config.in new file +15 -0
@@ -0,0 +1,15 @@ +config BR2_PACKAGE_PYTHON_GNUPG + bool "python-gnupg" + select BR2_PACKAGE_GNUPG2 if !BR2_PACKAGE_GNUPG # runtime + help + A wrapper for the Gnu Privacy Guard (GPG or GnuPG). + + The gnupg module allows Python programs to make use of the + functionality provided by the GNU Privacy Guard (abbreviated + GPG or GnuPG). Using this module, Python programs can + encrypt and decrypt data, digitally sign documents and + verify digital signatures, manage (generate, list and + delete) encryption keys, using Public Key Infrastructure + (PKI) encryption technology based on OpenPGP. + + https://docs.red-dove.com/python-gnupg/
package/python-gnupg/python-gnupg.hash new file +5 -0
@@ -0,0 +1,5 @@ +# md5, sha256 from https://pypi.org/pypi/python-gnupg/json +md5 02c5d77b8db9dfba0741627560d89bd5 python-gnupg-0.4.8.tar.gz +sha256 b64de1ae5cedf872b437201a566fa2c62ce0c95ea2e30177eb53aee1258507d7 python-gnupg-0.4.8.tar.gz +# Locally computed sha256 checksums +sha256 9620da3d3afdfca7dea53c4375c1507ab2d3a4af4e706827023acb49a9ec4a5e LICENSE.txt
package/python-gnupg/python-gnupg.mk new file +13 -0
@@ -0,0 +1,13 @@ +################################################################################ +# +# python-gnupg +# +################################################################################ + +PYTHON_GNUPG_VERSION = 0.4.8 +PYTHON_GNUPG_SITE = https://files.pythonhosted.org/packages/b1/90/75e15ead9693028c05fc7abd25c756c0d1da27bf04a27d6f5c4139d8ee10 +PYTHON_GNUPG_LICENSE = BSD-3-Clause +PYTHON_GNUPG_LICENSE_FILES = LICENSE.txt +PYTHON_GNUPG_SETUP_TYPE = setuptools + +$(eval $(python-package))
Signature · 6 lines
2.34.1 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hello Julien,
Quoted 6 lines · On Mon, 10 Jan 2022 21:01:51 +0100 Julien Olivain <[email protected]> wrote:
DEVELOPERS | 1 + package/Config.in | 1 + package/python-gnupg/Config.in | 15 +++++++++++++++ package/python-gnupg/python-gnupg.hash | 5 +++++ package/python-gnupg/python-gnupg.mk | 13 +++++++++++++ 5 files changed, 35 insertions(+)
Thanks for the patch, which I have applied, with a change (see below). However, more importantly, could you write and contribute a test case for python-gnupg in our runtime test infrastructure ? See
https://buildroot.org/downloads/manual/manual.html#_using_the_runtime_tests_framework
for some amount of details.
package/python-gnupg/Config.in line 3
Quoted 3 lines
package/python-gnupg/Config.in new file +3
-0+config BR2_PACKAGE_PYTHON_GNUPG + bool "python-gnupg" + select BR2_PACKAGE_GNUPG2 if !BR2_PACKAGE_GNUPG # runtime
This generates a circular dependency reported by kconfig, because another package does exactly the opposite. So I have inverted the logic here:
select BR2_PACKAGE_GNUPG if !BR2_PACKAGE_GNUPG2 # runtime
Best regards,
Thomas
Signature · 7 lines
Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering and training https://bootlin.com _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Thomas,
Quoted 14 lines · Thomas Petazzoni
Hello Julien,
package/python-gnupg/Config.in line 3
Quoted 4 lines · On Mon, 10 Jan 2022 21:01:51 +0100 Julien Olivain <[email protected]> wrote:
[...]
package/python-gnupg/Config.in new file +3
-0+config BR2_PACKAGE_PYTHON_GNUPG + bool "python-gnupg" + select BR2_PACKAGE_GNUPG2 if !BR2_PACKAGE_GNUPG # runtimeThis generates a circular dependency reported by kconfig, because another package does exactly the opposite. So I have inverted the logic here:
Quoted 1 line
select
BR2_PACKAGE_GNUPGif !BR2_PACKAGE_GNUPG2 # runtime
What do you think about reversing the logic of all Buildroot packages selecting gnupg so they default to gnupg2?
Quoting: https://gnupg.org/download/index.html
"""
GnuPG 1.4 is the old, single binary version which still support the unsafe PGP-2 keys. This branch has no dependencies on the above listed libraries or the Pinentry. However, it lacks many modern features and will receive only important updates.
"""
There is currently only two packages selecting gnupg:
gpgme and python-gnupg
Most Linux distributions are now shipping gnupg2 by default. gnupg v1 is now more for legacy/compatibility cases.
If you agree, I can send a patch for this.
Best regards,
Julien.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 30 lines · Julien Olivain
Hi Thomas,
Quoted 10 lines · Thomas Petazzoni
Hello Julien,
Quoted 4 lines · On Mon, 10 Jan 2022 21:01:51 +0100 Julien Olivain <[email protected]> wrote:
[...]
+configBR2_PACKAGE_PYTHON_GNUPG
+ bool "python-gnupg"
+ selectBR2_PACKAGE_GNUPG2if !BR2_PACKAGE_GNUPG # runtimeQuoted 5 lines
This generates a circular dependency reported by kconfig, because another package does exactly the opposite. So I have inverted the logic here:
select
BR2_PACKAGE_GNUPGif !BR2_PACKAGE_GNUPG2 # runtimeWhat do you think about reversing the logic of all Buildroot packages selecting gnupg so they default to gnupg2?
Quoting: https://gnupg.org/download/index.html
"""
GnuPG 1.4 is the old, single binary version which still support the unsafe PGP-2 keys. This branch has no dependencies on the above listed libraries or the Pinentry. However, it lacks many modern features and will receive only important updates.
"""
Quoted 5 lines
There is currently only two packages selecting gnupg:
gpgme and python-gnupgMost Linux distributions are now shipping gnupg2 by default. gnupg v1 is now more for legacy/compatibility cases.
Perhaps we should simply remove gnupg instead. We've had gnupg2 for 7.5 years
now, that should be enough to migrate.
Regards,
Arnout
Quoted 10 lines
If you agree, I can send a patch for this.
Best regards,
Julien.
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Arnout,
Quoted 34 lines · arnout at mind.be
Quoted 33 lines · Julien Olivain
Hi Thomas,
Quoted 10 lines · Thomas Petazzoni
Hello Julien,
Quoted 4 lines · On Mon, 10 Jan 2022 21:01:51 +0100 Julien Olivain <ju.o at free.fr> wrote:
?[...]
+configBR2_PACKAGE_PYTHON_GNUPG
+??? bool "python-gnupg"
+??? selectBR2_PACKAGE_GNUPG2if !BR2_PACKAGE_GNUPG # runtimeQuoted 5 lines
This generates a circular dependency reported by kconfig, because another package does exactly the opposite. So I have inverted the logic here:
select
BR2_PACKAGE_GNUPGif !BR2_PACKAGE_GNUPG2 # runtimeWhat do you think about reversing the logic of all Buildroot packages selecting gnupg so they default to gnupg2?
Quoting: https://gnupg.org/download/index.html
"""
GnuPG 1.4 is the old, single binary version which still support the unsafe PGP-2 keys. This branch has no dependencies on the above listed libraries or the Pinentry. However, it lacks many modern features and will receive only important updates.
"""There is currently only two packages selecting gnupg:
gpgme and python-gnupg
Quoted 6 lines
Quoted 2 lines
Most Linux distributions are now shipping gnupg2 by default.? gnupg v1 is now more for legacy/compatibility cases.
Perhaps we should simply remove gnupg instead. We've had gnupg2 for
7.5 years
now, that should be enough to migrate.
I think gnupg (version 1) should be kept in Buildroot:
- it's still maintained (only for important updates),
- it has a smaller footprint (compared to v2),
- it has less dependencies (only zlib),
- it has less build dependencies (can build static, no need for MMU/threads, ...)
gnupg1 might still be useful in some specific cases. This is why I was mentioning to switch the default version to v2, rather than removing v1.
Best regards,
Julien.
Quoted 13 lines
Regards,
ArnoutQuoted 10 lines
If you agree, I can send a patch for this.
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot at buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot