git: 4cead7b4ae3b - main - devel/py-decorator: Convert to USE_PYTHON=pep517

From: Po-Chuan Hsieh <sunpoet_at_FreeBSD.org>
Date: Wed, 18 Sep 2024 06:19:23 UTC
The branch main has been updated by sunpoet:

URL: https://cgit.FreeBSD.org/ports/commit/?id=4cead7b4ae3b35a46284c98cffd9aad07cd7fd59

commit 4cead7b4ae3b35a46284c98cffd9aad07cd7fd59
Author:     Po-Chuan Hsieh <sunpoet@FreeBSD.org>
AuthorDate: 2024-09-18 05:56:25 +0000
Commit:     Po-Chuan Hsieh <sunpoet@FreeBSD.org>
CommitDate: 2024-09-18 06:13:13 +0000

    devel/py-decorator: Convert to USE_PYTHON=pep517
    
    - Update pkg-descr
    - Bump PORTREVISION for package change
---
 devel/py-decorator/Makefile  |  9 +++++++--
 devel/py-decorator/pkg-descr | 17 +++++------------
 2 files changed, 12 insertions(+), 14 deletions(-)

diff --git a/devel/py-decorator/Makefile b/devel/py-decorator/Makefile
index 87872456d9f9..befa6f991ff1 100644
--- a/devel/py-decorator/Makefile
+++ b/devel/py-decorator/Makefile
@@ -1,5 +1,6 @@
 PORTNAME=	decorator
 PORTVERSION=	5.1.1
+PORTREVISION=	1
 CATEGORIES=	devel python
 MASTER_SITES=	PYPI
 PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
@@ -11,12 +12,16 @@ WWW=		https://github.com/micheles/decorator
 LICENSE=	MIT
 LICENSE_FILE=	${WRKSRC}/LICENSE.txt
 
+BUILD_DEPENDS=	${PYTHON_PKGNAMEPREFIX}setuptools>=0:devel/py-setuptools@${PY_FLAVOR} \
+		${PYTHON_PKGNAMEPREFIX}wheel>=0:devel/py-wheel@${PY_FLAVOR}
+
 USES=		cpe python
-CPE_VENDOR=	python
-USE_PYTHON=	autoplist distutils
+USE_PYTHON=	autoplist concurrent pep517
 
 NO_ARCH=	yes
 
+CPE_VENDOR=	python
+
 do-test:
 	@cd ${WRKSRC} && ${PYTHON_CMD} ${PYDISTUTILS_SETUP} test
 
diff --git a/devel/py-decorator/pkg-descr b/devel/py-decorator/pkg-descr
index 2ed7f2f97559..f3111f97d40b 100644
--- a/devel/py-decorator/pkg-descr
+++ b/devel/py-decorator/pkg-descr
@@ -1,12 +1,5 @@
-As of now, writing custom decorators correctly requires some
-experience and it is not as easy as it could be. For instance, typical
-implementations of decorators involve nested functions, and we all
-know that flat is better than nested. Moreover, typical
-implementations of decorators do not preserve the signature of
-decorated functions, thus confusing both documentation tools and
-developers.
-
-The aim of the decorator module it to simplify the usage of decorators
-for the average programmer, and to popularize decorators usage giving
-examples of useful decorators, such as memoize, tracing,
-redirecting_stdout, locked, etc.
+The goal of the decorator module is to make it easy to define
+signature-preserving function decorators and decorator factories. It also
+includes an implementation of multiple dispatch and other niceties (please check
+the docs). It is released under a two-clauses BSD license, i.e. basically you
+can do whatever you want with it but I am not responsible.