Changeset View
Changeset View
Standalone View
Standalone View
security/py-pycryptodome-test-vectors/Makefile
PORTNAME= pycryptodome-test-vectors | PORTNAME= pycryptodome-test-vectors | ||||
DISTVERSION= 1.0.10 | DISTVERSION= 1.0.12 | ||||
john_saltant.com: Will the tests pass if the 1.0.12 test vectors are used with the 3.16.0 release? If not, maybe… | |||||
Done Inline ActionsIt's not mentioned explicitly, but I think it's potentially implied in the original package split. From https://www.pycryptodome.org/src/changelog#id22 :
Since they share the same GH development repo, I would assume it's best to keep the test-vectors reasonably in sync with the other packages. ngie: It's not mentioned explicitly, but I think it's potentially implied in the original package… | |||||
CATEGORIES= security python | CATEGORIES= security python | ||||
MASTER_SITES= PYPI | MASTER_SITES= PYPI | ||||
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} | PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} | ||||
MAINTAINER= john@saltant.com | MAINTAINER= john@saltant.com | ||||
COMMENT= Optional test vectors for PyCryptodome and PyCryptodomeX | COMMENT= Optional test vectors for PyCryptodome and PyCryptodomeX | ||||
WWW= https://www.pycryptodome.org/ | WWW= https://www.pycryptodome.org/ | ||||
LICENSE= BSD2CLAUSE APACHE20 | LICENSE= BSD2CLAUSE APACHE20 | ||||
LICENSE_COMB= multi | LICENSE_COMB= multi | ||||
LICENSE_FILE= ${WRKSRC}/LICENSE.rst | LICENSE_FILE= ${WRKSRC}/LICENSE.rst | ||||
# Officially: 2.7, 3-5-3.10 (same as security/py-cryptodome) | # Officially: 2.7, 3-5-3.11 (same as security/py-cryptodome) | ||||
Done Inline ActionsAdd support for Python 3.11 is included in the 3.17 release. john_saltant.com: [[ https://github.com/Legrandin/pycryptodome/commit/d2296cd0052a8d4b89ec6ebd1130fdf96864af6d |… | |||||
USES= cpe python:3.7+ zip | USES= cpe python:3.7+ | ||||
CPE_VENDOR= python | CPE_VENDOR= python | ||||
USE_PYTHON= autoplist distutils | USE_PYTHON= autoplist distutils | ||||
NO_ARCH= yes | NO_ARCH= yes | ||||
.include <bsd.port.mk> | .include <bsd.port.mk> |
Will the tests pass if the 1.0.12 test vectors are used with the 3.16.0 release? If not, maybe a dependency with minimum version spec would be appropriate?