diff options
| author | gdt <gdt> | 2012-03-20 23:38:26 +0000 |
|---|---|---|
| committer | gdt <gdt> | 2012-03-20 23:38:26 +0000 |
| commit | d1c94475d4365739931a4c27241124a54c4d31cd (patch) | |
| tree | 6f8f5506524280e6b065512523d6a565637fefe0 /security/py-cryptopp | |
| parent | 17f62f28752c727c12b4e2efb02529b0fe1b62f9 (diff) | |
| download | pkgsrc-d1c94475d4365739931a4c27241124a54c4d31cd.tar.gz | |
Split version into sane and excessive parts.
Upstream's version is 0.6.0.X, where X appears to be a large integer
in decimal that corresponds to a git sha1 has. Such large numbers
violate the assumption, true with just about every previous package,
that version number components will fit in an int --- code that
handles version numbers does not use a multiprecision integer library
like gmp. To address this, split the version into what would have
been the version under normal procedures (0.6.0), and put the bignum
into ${VERSION_EXCESSIVE}, allowing it be used in DISTNAME but not
PKGNAME.
Diffstat (limited to 'security/py-cryptopp')
| -rw-r--r-- | security/py-cryptopp/Makefile | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/security/py-cryptopp/Makefile b/security/py-cryptopp/Makefile index 927259caaf6..47082fb71fe 100644 --- a/security/py-cryptopp/Makefile +++ b/security/py-cryptopp/Makefile @@ -1,8 +1,9 @@ -# $NetBSD: Makefile,v 1.7 2012/03/16 00:14:36 gdt Exp $ +# $NetBSD: Makefile,v 1.8 2012/03/20 23:38:26 gdt Exp $ # -VERSION= 0.6.0.1206569328141510525648634803928199668821045408958 -DISTNAME= pycryptopp-${VERSION} +VERSION= 0.6.0 +VERSION_EXCESSIVE= 1206569328141510525648634803928199668821045408958 +DISTNAME= pycryptopp-${VERSION}.${VERSION_EXCESSIVE} PKGNAME= ${PYPKGPREFIX}-cryptopp-${VERSION} CATEGORIES= security python MASTER_SITES= http://pypi.python.org/packages/source/p/pycryptopp/ |