aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPo-Chuan Hsieh <sunpoet@FreeBSD.org>2023-04-19 10:54:11 +0000
committerPo-Chuan Hsieh <sunpoet@FreeBSD.org>2023-04-19 10:54:11 +0000
commitcb9b7eaf32fde0a536ad173c401ed0899d0f18d3 (patch)
tree93fa0213e08f8c3dcd0c2f13586faf8cddf8ff2f
parent6f656934f1aac9adb640591967820bf67578a9ca (diff)
downloadports-cb9b7eaf32fde0a536ad173c401ed0899d0f18d3.tar.gz
ports-cb9b7eaf32fde0a536ad173c401ed0899d0f18d3.zip
devel/py-versioneer: Add py-versioneer 0.28
Versioneer is a tool for managing a recorded version number in setuptools-based python projects. The goal is to remove the tedious and error-prone "update the embedded version string" step from your release process. Making a new release should be as easy as recording a new tag in your version-control system, and maybe making new tarballs.
-rw-r--r--devel/Makefile1
-rw-r--r--devel/py-versioneer/Makefile35
-rw-r--r--devel/py-versioneer/distinfo3
-rw-r--r--devel/py-versioneer/pkg-descr5
4 files changed, 44 insertions, 0 deletions
diff --git a/devel/Makefile b/devel/Makefile
index 6652c9caa5c0..70e991700b32 100644
--- a/devel/Makefile
+++ b/devel/Makefile
@@ -5635,6 +5635,7 @@
SUBDIR += py-vcversioner
SUBDIR += py-venusian
SUBDIR += py-verboselogs
+ SUBDIR += py-versioneer
SUBDIR += py-versiontools
SUBDIR += py-verspec
SUBDIR += py-vine
diff --git a/devel/py-versioneer/Makefile b/devel/py-versioneer/Makefile
new file mode 100644
index 000000000000..ce2696d6f995
--- /dev/null
+++ b/devel/py-versioneer/Makefile
@@ -0,0 +1,35 @@
+PORTNAME= versioneer
+PORTVERSION= 0.28
+CATEGORIES= devel python
+MASTER_SITES= PYPI
+PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
+
+MAINTAINER= sunpoet@FreeBSD.org
+COMMENT= Easy VCS-based management of project version strings
+WWW= https://github.com/python-versioneer/python-versioneer
+
+LICENSE= UNLICENSE
+LICENSE_FILE= ${WRKSRC}/LICENSE
+
+BUILD_DEPENDS= ${PYTHON_PKGNAMEPREFIX}setuptools>=0:devel/py-setuptools@${PY_FLAVOR} \
+ ${PYTHON_PKGNAMEPREFIX}wheel>=0:devel/py-wheel@${PY_FLAVOR}
+
+USES= python:3.7+
+USE_PYTHON= autoplist concurrent pep517
+
+NO_ARCH= yes
+
+OPTIONS_DEFINE= TOML
+OPTIONS_DEFAULT=TOML
+TOML_DESC= TOML (Tom's Obvious Minimal Language) support
+
+.include <bsd.port.pre.mk>
+
+.if ${PYTHON_REL} < 31100
+BUILD_DEPENDS+= ${PYTHON_PKGNAMEPREFIX}tomli>=0:textproc/py-tomli@${PY_FLAVOR}
+.if ${PORT_OPTIONS:MTOML}
+RUN_DEPENDS+= ${PYTHON_PKGNAMEPREFIX}tomli>=0:textproc/py-tomli@${PY_FLAVOR}
+.endif
+.endif
+
+.include <bsd.port.post.mk>
diff --git a/devel/py-versioneer/distinfo b/devel/py-versioneer/distinfo
new file mode 100644
index 000000000000..511d168bd94b
--- /dev/null
+++ b/devel/py-versioneer/distinfo
@@ -0,0 +1,3 @@
+TIMESTAMP = 1681846806
+SHA256 (versioneer-0.28.tar.gz) = 7175ca8e7bb4dd0e3c9779dd2745e5b4a6036304af3f5e50bd896f10196586d6
+SIZE (versioneer-0.28.tar.gz) = 74466
diff --git a/devel/py-versioneer/pkg-descr b/devel/py-versioneer/pkg-descr
new file mode 100644
index 000000000000..91f2b4326b19
--- /dev/null
+++ b/devel/py-versioneer/pkg-descr
@@ -0,0 +1,5 @@
+Versioneer is a tool for managing a recorded version number in setuptools-based
+python projects. The goal is to remove the tedious and error-prone "update the
+embedded version string" step from your release process. Making a new release
+should be as easy as recording a new tag in your version-control system, and
+maybe making new tarballs.