package/python-pyaes: new package
PATCH v2 1/2 package/python-pyaes: new package
--- DEVELOPERS | 1 + package/Config.in | 1 + package/python-pyaes/Config.in | 7 +++++++ package/python-pyaes/python-pyaes.hash | 5 +++++ package/python-pyaes/python-pyaes.mk | 14 ++++++++++++++ 5 files changed, 28 insertions(+) create mode 100644 package/python-pyaes/Config.in create mode 100644 package/python-pyaes/python-pyaes.hash create mode 100644 package/python-pyaes/python-pyaes.mk
DEVELOPERS +1 -0
@@ -258,6 +258,7 @@ F: package/orbit/ N: Bartosz Bilas <[email protected]> F: package/qt5/qt5scxml/ F: package/qt5/qt5webview/ +F: package/python-pyaes N: Bartosz Golaszewski <[email protected]> F: package/autoconf-archive/
package/Config.in +1 -0
@@ -1006,6 +1006,7 @@ menu "External python modules" source "package/python-ptyprocess/Config.in" source "package/python-pudb/Config.in" source "package/python-py/Config.in" + source "package/python-pyaes/Config.in" source "package/python-pyasn/Config.in" source "package/python-pyasn-modules/Config.in" source "package/python-pyasn1/Config.in"
package/python-pyaes/Config.in new file +7 -0
@@ -0,0 +1,7 @@ +config BR2_PACKAGE_PYTHON_PYAES + bool "python-pyaes" + help + Pure-Python Implementation of the AES block-cipher and + common modes of operation. + + https://github.com/ricmoo/pyaes
package/python-pyaes/python-pyaes.hash new file +5 -0
@@ -0,0 +1,5 @@ +# md5, sha256 from https://pypi.org/pypi/pyaes/json +md5 20fd5c6e29dcfdd08098e85a859a54ec pyaes-1.6.1.tar.gz +sha256 02c1b1405c38d3c370b085fb952dd8bea3fadcee6411ad99f312cc129c536d8f pyaes-1.6.1.tar.gz +# Locally computed sha256 checksums +sha256 1efe6c78b28b4203d397ea9b68bdc9c658d21cd9afaf8ae8223def83f2a7ebbd LICENSE.txt
package/python-pyaes/python-pyaes.mk new file +14 -0
@@ -0,0 +1,14 @@ +################################################################################ +# +# python-pyaes +# +################################################################################ + +PYTHON_PYAES_VERSION = 1.6.1 +PYTHON_PYAES_SOURCE = pyaes-$(PYTHON_PYAES_VERSION).tar.gz +PYTHON_PYAES_SITE = https://files.pythonhosted.org/packages/44/66/2c17bae31c906613795711fc78045c285048168919ace2220daa372c7d72 +PYTHON_PYAES_SETUP_TYPE = distutils +PYTHON_PYAES_LICENSE = MIT +PYTHON_PYAES_LICENSE_FILES = LICENSE.txt + +$(eval $(python-package))
Signature · 1 line
2.24.0
PATCH v2 2/2 package/python-esptool: new package
---
Changes v1 -> v2:
- Use existing python-serial package
instead of creating a new python-pyserial.
DEVELOPERS | 1 + package/Config.in | 1 + package/python-esptool/Config.in | 10 ++++++++++ package/python-esptool/python-esptool.hash | 5 +++++ package/python-esptool/python-esptool.mk | 14 ++++++++++++++ 5 files changed, 31 insertions(+) create mode 100644 package/python-esptool/Config.in create mode 100644 package/python-esptool/python-esptool.hash create mode 100644 package/python-esptool/python-esptool.mk
DEVELOPERS +1 -0
@@ -259,6 +259,7 @@ N: Bartosz Bilas <[email protected]> F: package/qt5/qt5scxml/ F: package/qt5/qt5webview/ F: package/python-pyaes +F: package/python-esptool N: Bartosz Golaszewski <[email protected]> F: package/autoconf-archive/
package/Config.in +1 -0
@@ -902,6 +902,7 @@ menu "External python modules" source "package/python-engineio/Config.in" source "package/python-enum/Config.in" source "package/python-enum34/Config.in" + source "package/python-esptool/Config.in" source "package/python-falcon/Config.in" source "package/python-fire/Config.in" source "package/python-flask/Config.in"
package/python-esptool/Config.in new file +10 -0
@@ -0,0 +1,10 @@ +config BR2_PACKAGE_PYTHON_ESPTOOL + bool "python-esptool" + select BR2_PACKAGE_PYTHON_SERIAL # runtime + select BR2_PACKAGE_PYTHON_PYAES # runtime + select BR2_PACKAGE_PYTHON_ECDSA # runtime + help + A serial utility to communicate & flash code to Espressif + ESP8266 & ESP32 chips. + + https://github.com/espressif/esptool
package/python-esptool/python-esptool.hash new file +5 -0
@@ -0,0 +1,5 @@ +# md5, sha256 from https://pypi.org/pypi/esptool/json +md5 d17b9293910773045b9de0d5caa0597d esptool-2.8.tar.gz +sha256 1e4288d9f00e55ba36809cc79c493643c623bfa036d7b019a0ebe396284bc317 esptool-2.8.tar.gz +# Locally computed sha256 checksums +sha256 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643 LICENSE
package/python-esptool/python-esptool.mk new file +14 -0
@@ -0,0 +1,14 @@ +################################################################################ +# +# python-esptool +# +################################################################################ + +PYTHON_ESPTOOL_VERSION = 2.8 +PYTHON_ESPTOOL_SOURCE = esptool-$(PYTHON_ESPTOOL_VERSION).tar.gz +PYTHON_ESPTOOL_SITE = https://files.pythonhosted.org/packages/68/91/08c182f66fa3f12a96e754ae8ec7762abb2d778429834638f5746f81977a +PYTHON_ESPTOOL_SETUP_TYPE = setuptools +PYTHON_ESPTOOL_LICENSE = GNU General Public License v2 or later (GPLv2+) +PYTHON_ESPTOOL_LICENSE_FILES = LICENSE + +$(eval $(python-package))
Signature · 1 line
2.24.0
Thomas Petazzoni
AppliedPATCH v2 2/2 package/python-esptool: new package
Hello Bartosz,
DEVELOPERS N: Bartosz Bilas <[email protected]> · line 262
Quoted 9 lines · On Thu, 7 Nov 2019 18:05:04 +0100 Bartosz Bilas <[email protected]>…
DEVELOPERS +1
-0@@ -259,6 +259,7 @@ N: Bartosz Bilas <[email protected]> F: package/qt5/qt5scxml/ F: package/qt5/qt5webview/ F: package/python-pyaes +F: package/python-esptool
Alphabetic ordering + final /.
package/python-esptool/Config.in line 5
Quoted 11 lines
package/python-esptool/Config.in new file +5
-0@@ -0,0 +1,10 @@ +config BR2_PACKAGE_PYTHON_ESPTOOL + bool "python-esptool" + select BR2_PACKAGE_PYTHON_SERIAL # runtime + select BR2_PACKAGE_PYTHON_PYAES # runtime + select BR2_PACKAGE_PYTHON_ECDSA # runtime
Alphabetic ordering.
package/python-esptool/Config.in line 6
Quoted 1 line
package/python-esptool/Config.in new file +1
-0+PYTHON_ESPTOOL_LICENSE = GNU General Public License v2 or later (GPLv2+)
The proper way to describe this is just:
PYTHON_ESPTOOL_LICENSE = GPL-2.0+
Applied to next with those different issues fixed. Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH v2 2/2 package/python-esptool: new package
Hello Thomas,
Quoted 17 lines · Thomas Petazzoni
Hello Bartosz,
DEVELOPERS N: Bartosz Bilas <[email protected]> · line 262
Quoted 9 lines · On Thu, 7 Nov 2019 18:05:04 +0100 Bartosz Bilas <[email protected]>…
DEVELOPERS +1
-0@@ -259,6 +259,7 @@ N: Bartosz Bilas <[email protected]> F: package/qt5/qt5scxml/ F: package/qt5/qt5webview/ F: package/python-pyaes +F: package/python-esptoolAlphabetic ordering + final /.
Quoted 12 lines
package/python-esptool/Config.in line 5
Quoted 11 lines
package/python-esptool/Config.in new file +5
-0@@ -0,0 +1,10 @@ +config BR2_PACKAGE_PYTHON_ESPTOOL + bool "python-esptool" + select BR2_PACKAGE_PYTHON_SERIAL # runtime + select BR2_PACKAGE_PYTHON_PYAES # runtime + select BR2_PACKAGE_PYTHON_ECDSA # runtimeAlphabetic ordering.
This and
Quoted 5 lines
package/python-esptool/Config.in line 6
Quoted 2 lines
package/python-esptool/Config.in new file +1
-0+PYTHON_ESPTOOL_LICENSE = GNU General Public License v2 or later (GPLv2+)The proper way to describe this is just:
PYTHON_ESPTOOL_LICENSE= GPL-2.0+
this was created using scanpypi script so do you think we should fix that script or adjust that manually as you did?
Best
Bartek
Quoted 4 lines
Applied to next with those different issues fixed. Thanks!
Thomas
PATCH v2 2/2 package/python-esptool: new package
Hello,
+Yegor in Cc.
Quoted 7 lines · On Fri, 8 Nov 2019 09:45:50 +0100 Bartosz Bilas <[email protected]>…
Quoted 4 lines
Quoted 1 line
+PYTHON_ESPTOOL_LICENSE = GNU General Public License v2 or later (GPLv2+)
The proper way to describe this is just:
PYTHON_ESPTOOL_LICENSE= GPL-2.0+this was created using scanpypi script so do you think we should fix that script or adjust that manually as you did?
scanpipy already has a conversion table between Pipy-provided license strings and Buildroot license tags:
'Apache Software License': 'Apache-2.0',
'BSD License': 'FIXME: please specify the exact BSD version', 'European Union Public Licence 1.0': 'EUPL-1.0', 'European Union Public Licence 1.1': 'EUPL-1.1', "GNU General Public License": "GPL",
"GNU General Public License v2": "GPL-2.0",
"GNU General Public License v2 or later": "GPL-2.0+", "GNU General Public License v3": "GPL-3.0",
"GNU General Public License v3 or later": "GPL-3.0+", "GNU Lesser General Public License v2": "LGPL-2.1", "GNU Lesser General Public License v2 or later": "LGPL-2.1+", "GNU Lesser General Public License v3": "LGPL-3.0", "GNU Lesser General Public License v3 or later": "LGPL-3.0+", "GNU Library or Lesser General Public License": "LGPL-2.0", "ISC License": "ISC",
"MIT License": "MIT",
"Mozilla Public License 1.0": "MPL-1.0",
"Mozilla Public License 1.1": "MPL-1.1",
"Mozilla Public License 2.0": "MPL-2.0",
"Zope Public License": "ZPL"
Obviously, the value "GNU General Public License v2 or later (GPLv2+)" that was used by this package didn't match any entry in this table. Since "GNU General Public License v2 or later (GPLv2+)" is apparently rarely used, I don't think it's worth adding an entry to the table: for such cases, we simply have to do a manual fixup. In any case, ./utils/scanpipy does not guarantee that it provides a fully working and correct Buildroot package: it extracts most information from Pipy, but a careful review, and possibly some changes may be necessary.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH v2 2/2 package/python-esptool: new package
Moin moin!
Quoted 40 lines · Thomas Petazzoni
Hello,
+Yegor in Cc.
Quoted 7 lines · On Fri, 8 Nov 2019 09:45:50 +0100 Bartosz Bilas <[email protected]>…
Quoted 4 lines
Quoted 1 line
+PYTHON_ESPTOOL_LICENSE = GNU General Public License v2 or later (GPLv2+)
The proper way to describe this is just:
PYTHON_ESPTOOL_LICENSE= GPL-2.0+this was created using scanpypi script so do you think we should fix that script or adjust that manually as you did?
scanpipy already has a conversion table between Pipy-provided license strings and Buildroot license tags:
'Apache Software License': 'Apache-2.0',
'BSD License': 'FIXME: please specify the exact BSD version', 'European Union Public Licence 1.0': 'EUPL-1.0', 'European Union Public Licence 1.1': 'EUPL-1.1', "GNU General Public License": "GPL",
"GNU General Public License v2": "GPL-2.0",
"GNU General Public License v2 or later": "GPL-2.0+", "GNU General Public License v3": "GPL-3.0",
"GNU General Public License v3 or later": "GPL-3.0+", "GNU Lesser General Public License v2": "LGPL-2.1", "GNU Lesser General Public License v2 or later": "LGPL-2.1+", "GNU Lesser General Public License v3": "LGPL-3.0", "GNU Lesser General Public License v3 or later": "LGPL-3.0+", "GNU Library or Lesser General Public License": "LGPL-2.0", "ISC License": "ISC",
"MIT License": "MIT",
"Mozilla Public License 1.0": "MPL-1.0",
"Mozilla Public License 1.1": "MPL-1.1",
"Mozilla Public License 2.0": "MPL-2.0",
"Zope Public License": "ZPL"
Quoted 8 lines
Obviously, the value "GNU General Public License v2 or later (GPLv2+)" that was used by this package didn't match any entry in this table. Since "GNU General Public License v2 or later (GPLv2+)" is apparently rarely used, I don't think it's worth adding an entry to the table: for such cases, we simply have to do a manual fixup. In any case, ./utils/scanpipy does not guarantee that it provides a fully working and correct Buildroot package: it extracts most information from Pipy, but a careful review, and possibly some changes may be necessary.
And one more thing. This table won't be used if you have installed the spdx package. But even this is not 100% correct as the license text doesn't determine whether it is GPL-2.0 or PGL-2.0+. It is stated in the source code.
The best thing would be if all projects would adhere to REUSE layout and SPDX identifiers [1].
[1] https://reuse.software/spec/
Best regards,
Yegor
PATCH v2 2/2 package/python-esptool: new package
In reply to Thomas PetazzoniHello guys,
Quoted 37 lines · Thomas Petazzoni
Hello,
+Yegor in Cc.
Quoted 6 lines · On Fri, 8 Nov 2019 09:45:50 +0100 Bartosz Bilas <[email protected]>…
Quoted 4 lines
Quoted 1 line
+PYTHON_ESPTOOL_LICENSE = GNU General Public License v2 or later (GPLv2+)
The proper way to describe this is just:
PYTHON_ESPTOOL_LICENSE= GPL-2.0+this was created using scanpypi script so do you think we should fix that script or adjust that manually as you did?
scanpipy already has a conversion table between Pipy-provided license strings and Buildroot license tags:
'Apache Software License': 'Apache-2.0',
'BSD License': 'FIXME: please specify the exact BSD version', 'European Union Public Licence 1.0': 'EUPL-1.0', 'European Union Public Licence 1.1': 'EUPL-1.1', "GNU General Public License": "GPL",
"GNU General Public License v2": "GPL-2.0",
"GNU General Public License v2 or later": "GPL-2.0+", "GNU General Public License v3": "GPL-3.0",
"GNU General Public License v3 or later": "GPL-3.0+", "GNU Lesser General Public License v2": "LGPL-2.1", "GNU Lesser General Public License v2 or later": "LGPL-2.1+", "GNU Lesser General Public License v3": "LGPL-3.0", "GNU Lesser General Public License v3 or later": "LGPL-3.0+", "GNU Library or Lesser General Public License": "LGPL-2.0", "ISC License": "ISC",
"MIT License": "MIT",
"Mozilla Public License 1.0": "MPL-1.0", "Mozilla Public License 1.1": "MPL-1.1", "Mozilla Public License 2.0": "MPL-2.0",
"Zope Public License": "ZPL"
Quoted 8 lines
Obviously, the value "GNU General Public License v2 or later (GPLv2+)" that was used by this package didn't match any entry in this table. Since "GNU General Public License v2 or later (GPLv2+)" is apparently rarely used, I don't think it's worth adding an entry to the table: for such cases, we simply have to do a manual fixup. In any case, ./utils/scanpipy does not guarantee that it provides a fully working and correct Buildroot package: it extracts most information from Pipy, but a careful review, and possibly some changes may be necessary.
I assume that's the same for that comment bellow:
Quoted 5 lines
+config
BR2_PACKAGE_PYTHON_ESPTOOL
+??? bool "python-esptool"
+??? selectBR2_PACKAGE_PYTHON_SERIAL# runtime
+??? selectBR2_PACKAGE_PYTHON_PYAES# runtime
+??? selectBR2_PACKAGE_PYTHON_ECDSA# runtime
Alphabetic ordering.
but I think it wouldn't be difficult to handle it in the script.
Best
Bartek
Quoted 4 lines
Best regards,
Thomas
PATCH v2 2/2 package/python-esptool: new package
Hello,
I've forgotten about Yegor in Cc.
Best
Bartek
Quoted 76 lines · Bartosz Bilas
Hello guys,
Quoted 42 lines · Thomas Petazzoni
Hello,
+Yegor in Cc.
Quoted 7 lines · On Fri, 8 Nov 2019 09:45:50 +0100 Bartosz Bilas <[email protected]>…
Quoted 5 lines
Quoted 2 lines
+PYTHON_ESPTOOL_LICENSE = GNU General Public License v2 or later (GPLv2+)
The proper way to describe this is just:
PYTHON_ESPTOOL_LICENSE= GPL-2.0+this was created using scanpypi script so do you think we should fix that script or adjust that manually as you did?
scanpipy already has a conversion table between Pipy-provided license strings and Buildroot license tags:
???????????????? 'Apache Software License': 'Apache-2.0', ???????????????? 'BSD License': 'FIXME: please specify the exact BSD version',
???????????????? 'European Union Public Licence 1.0': 'EUPL-1.0', ???????????????? 'European Union Public Licence 1.1': 'EUPL-1.1', ???????????????? "GNU General Public License": "GPL", ???????????????? "GNU General Public License v2": "GPL-2.0", ???????????????? "GNU General Public License v2 or later": "GPL-2.0+", ???????????????? "GNU General Public License v3": "GPL-3.0", ???????????????? "GNU General Public License v3 or later": "GPL-3.0+", ???????????????? "GNU Lesser General Public License v2": "LGPL-2.1", ???????????????? "GNU Lesser General Public License v2 or later":
"LGPL-2.1+",
???????????????? "GNU Lesser General Public License v3": "LGPL-3.0", ???????????????? "GNU Lesser General Public License v3 or later":
"LGPL-3.0+",
???????????????? "GNU Library or Lesser General Public License":
"LGPL-2.0",
???????????????? "ISC License": "ISC",
???????????????? "MIT License": "MIT",
???????????????? "Mozilla Public License 1.0": "MPL-1.0", ???????????????? "Mozilla Public License 1.1": "MPL-1.1", ???????????????? "Mozilla Public License 2.0": "MPL-2.0", ???????????????? "Zope Public License": "ZPL"Quoted 8 lines
Obviously, the value "GNU General Public License v2 or later (GPLv2+)" that was used by this package didn't match any entry in this table. Since "GNU General Public License v2 or later (GPLv2+)" is apparently rarely used, I don't think it's worth adding an entry to the table: for such cases, we simply have to do a manual fixup. In any case, ./utils/scanpipy does not guarantee that it provides a fully working and correct Buildroot package: it extracts most information from Pipy, but a careful review, and possibly some changes may be necessary.
I assume that's the same for that comment bellow:
Quoted 5 lines
+config
BR2_PACKAGE_PYTHON_ESPTOOL
+??? bool "python-esptool"
+??? selectBR2_PACKAGE_PYTHON_SERIAL# runtime
+??? selectBR2_PACKAGE_PYTHON_PYAES# runtime
+??? selectBR2_PACKAGE_PYTHON_ECDSA# runtimeAlphabetic ordering.
but I think it wouldn't be difficult to handle it in the script.
Best
BartekQuoted 4 lines
Best regards,
Thomas
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
PATCH v2 2/2 package/python-esptool: new package
In reply to Bartosz BilasQuoted 11 lines · On Fri, 8 Nov 2019 10:06:31 +0100 Bartosz Bilas <[email protected]>…
I assume that's the same for that comment bellow:
Quoted 5 lines
+config
BR2_PACKAGE_PYTHON_ESPTOOL
+??? bool "python-esptool"
+??? selectBR2_PACKAGE_PYTHON_SERIAL# runtime
+??? selectBR2_PACKAGE_PYTHON_PYAES# runtime
+??? selectBR2_PACKAGE_PYTHON_ECDSA# runtimeAlphabetic ordering.
but I think it wouldn't be difficult to handle it in the script.
Indeed, the alphabetic ordering here could I suppose be easily handled by the script.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Thomas Petazzoni
AppliedPATCH v2 1/2 package/python-pyaes: new package
In reply to Bartosz BilasHello Bartosz,
DEVELOPERS F: package/orbit/ · line 261
Quoted 9 lines · On Thu, 7 Nov 2019 18:05:03 +0100 Bartosz Bilas <[email protected]>…
DEVELOPERS +1
-0@@ -258,6 +258,7 @@ F: package/orbit/ N: Bartosz Bilas <[email protected]> F: package/qt5/qt5scxml/ F: package/qt5/qt5webview/ +F: package/python-pyaes
Alphabetic ordering + needs a final /, to be like other entries.
Applied to next after fixing this minor issue. Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com