From nobody Sat Apr 16 04:20:51 2022 X-Original-To: dev-commits-ports-main@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8AD095D5594; Sat, 16 Apr 2022 04:20:52 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KgKkW5ZNMz3LJK; Sat, 16 Apr 2022 04:20:51 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1650082852; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=jsssSmOnwv1BqqGiJ61dJve13CjJfoL7JthyHM282h8=; b=ZOiVp89PZ3wF4Vkcno024X1qJAX06UOQBurZrq3EKPhGT+uBWGM9y7LHq5hFuAf/4cfWQq 99ydpVpTUB21bG5DHidR2WLT1Y6OZzkYA3C6d/xvsvGzfCVd7iSg2sGZNrh94dJPqWlOhL pZ5W61p4bv4aLTOC9auVnxW+uaKHWzAp7cJm4BW5PnB6fn1DB6KTdjUZkSMwiujywW/dIw uaL4omgnn5w/yx1W5t4X30nKOkWvfox2dZez87TGGveLn32UGBRfNwQlNJty82mm76yexC 6hSNMIo4gq6AVAVq0gFBjz6GkET/hdwwVA8VuEFWIgKsfuMFdNJm13IaxYtb8Q== Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8422B22CBC; Sat, 16 Apr 2022 04:20:51 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 23G4Kpoq098520; Sat, 16 Apr 2022 04:20:51 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 23G4Kpdm098519; Sat, 16 Apr 2022 04:20:51 GMT (envelope-from git) Date: Sat, 16 Apr 2022 04:20:51 GMT Message-Id: <202204160420.23G4Kpdm098519@gitrepo.freebsd.org> To: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org From: Po-Chuan Hsieh Subject: git: 773af17f8ce9 - main - devel/py-validate-pyproject: Add py-validate-pyproject 0.7.1 List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-main@freebsd.org X-BeenThere: dev-commits-ports-main@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: sunpoet X-Git-Repository: ports X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 773af17f8ce91749a5c8c5e86fbb36612554e9f9 Auto-Submitted: auto-generated ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1650082852; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=jsssSmOnwv1BqqGiJ61dJve13CjJfoL7JthyHM282h8=; b=TzRM3SoCp9vCfPnREMMobXqW43vWnLNQlPzjrV7dqNkr0gcxAfwZiJDf+bxOJVHIK3c/wa 7u6E64lQFf+dwBptyiY2McNtNHU54mPZ5ev2DpflY2i29zMlGCHTWsMkVTz1+v1gBr9Tsf rg/3RlXev8bXYfqE+SfRpBjMf0Ky2jM8jkQhdno7/JVnHcLwdRWjZ127XYYSaiECC2vkpb AcOdMzbag/jRNLdHhhB49At4AP+YOkXn2cgWwi1/QYAEqD0dTvJ5enrvlHuUgzg+2e5s6E Tk1q2kmXFcBwfa8IOLEobcqIANeTQRUQouOadP5NyXH3nCJV20D+mKpImUxZhQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1650082852; a=rsa-sha256; cv=none; b=lujZE9xgEZHcROJbWT3w/fhHdXvKU1LSzu0Ao5ya937IIXIc6KdvpGvVuW0RBvi7RyXVi9 GRXJMAyh4m785elP4yCjUwEuI7IdIspfpsGG6l+cxSsRZSnIfRBWkbGifiJ3HoXHIy0bjm Hc587OlBPboNhSbFeEzBYn3JqXLi07WqZuXh4qio+gr0BHamzfSR2MgEL4MbZjHL1rRiCj Aiq6KAUO1CAYo8iTLLREKXLdS9nlnJh/Z7L1xSlKar0R0wY2vxy5sy/Lq2BJR0FW8cFcS/ wcxgU1/An3bind0g6IVw1Xw/YHVqzenizbhPsZBveRPT8fgwWmoEFGxJtSeadA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N The branch main has been updated by sunpoet: URL: https://cgit.FreeBSD.org/ports/commit/?id=773af17f8ce91749a5c8c5e86fbb36612554e9f9 commit 773af17f8ce91749a5c8c5e86fbb36612554e9f9 Author: Po-Chuan Hsieh AuthorDate: 2022-04-16 03:39:04 +0000 Commit: Po-Chuan Hsieh CommitDate: 2022-04-16 04:19:03 +0000 devel/py-validate-pyproject: Add py-validate-pyproject 0.7.1 With the approval of PEP 517 and PEP 518, the Python community shifted towards a strong focus on standardisation for packaging software, which allows more freedom when choosing tools during development and make sure packages created using different technologies can interoperate without the need for custom installation procedures. This shift became even more clear when PEP 621 was also approved, as a standardised way of specifying project metadata and dependencies. validate-pyproject was born in this context, with the mission of validating pyproject.toml files, and make sure they are compliant with the standards and PEPs. Behind the scenes, validate-pyproject relies on JSON Schema files, which, in turn, are also a standardised way of checking if a given data structure complies with a certain specification. WWW: https://github.com/abravalheri/validate-pyproject --- devel/Makefile | 1 + devel/py-validate-pyproject/Makefile | 36 +++++++++++++++++++++++++++++++++++ devel/py-validate-pyproject/distinfo | 3 +++ devel/py-validate-pyproject/pkg-descr | 16 ++++++++++++++++ 4 files changed, 56 insertions(+) diff --git a/devel/Makefile b/devel/Makefile index 73db3bbd92ac..0e54c0fa1d49 100644 --- a/devel/Makefile +++ b/devel/Makefile @@ -5380,6 +5380,7 @@ SUBDIR += py-user_agents SUBDIR += py-userpath SUBDIR += py-uvloop + SUBDIR += py-validate-pyproject SUBDIR += py-validators SUBDIR += py-validictory SUBDIR += py-vcrpy diff --git a/devel/py-validate-pyproject/Makefile b/devel/py-validate-pyproject/Makefile new file mode 100644 index 000000000000..b1c83f9bbd7e --- /dev/null +++ b/devel/py-validate-pyproject/Makefile @@ -0,0 +1,36 @@ +# Created by: Po-Chuan Hsieh + +PORTNAME= validate-pyproject +PORTVERSION= 0.7.1 +CATEGORIES= devel python +MASTER_SITES= CHEESESHOP +PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= Validation library and CLI tool for checking on pyproject.toml files using JSON schema + +LICENSE= MPL20 +LICENSE_FILE= ${WRKSRC}/LICENSE.txt + +BUILD_DEPENDS= ${PYTHON_PKGNAMEPREFIX}setuptools_scm>=5:devel/py-setuptools_scm@${PY_FLAVOR} + +USES= python:3.7+ +USE_PYTHON= autoplist concurrent distutils + +NO_ARCH= yes + +OPTIONS_DEFINE= ALL +OPTIONS_DEFAULT=ALL +ALL_DESC= All functions + +ALL_RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}packaging>=20.4:devel/py-packaging@${PY_FLAVOR} \ + ${PYTHON_PKGNAMEPREFIX}tomli>=1.2.1:textproc/py-tomli@${PY_FLAVOR} \ + ${PYTHON_PKGNAMEPREFIX}trove-classifiers>=2021.10.20:devel/py-trove-classifiers@${PY_FLAVOR} + +.include + +.if ${PYTHON_REL} < 30800 +RUN_DEPENDS+= ${PYTHON_PKGNAMEPREFIX}importlib-metadata>=0:devel/py-importlib-metadata@${PY_FLAVOR} +.endif + +.include diff --git a/devel/py-validate-pyproject/distinfo b/devel/py-validate-pyproject/distinfo new file mode 100644 index 000000000000..543c28cc419c --- /dev/null +++ b/devel/py-validate-pyproject/distinfo @@ -0,0 +1,3 @@ +TIMESTAMP = 1649423648 +SHA256 (validate-pyproject-0.7.1.tar.gz) = e5ea929a373c7cddb7a7fc34fe4999b341fc4d98fb0a19e570be09f92fb438a4 +SIZE (validate-pyproject-0.7.1.tar.gz) = 102987 diff --git a/devel/py-validate-pyproject/pkg-descr b/devel/py-validate-pyproject/pkg-descr new file mode 100644 index 000000000000..81e204851424 --- /dev/null +++ b/devel/py-validate-pyproject/pkg-descr @@ -0,0 +1,16 @@ +With the approval of PEP 517 and PEP 518, the Python community shifted towards a +strong focus on standardisation for packaging software, which allows more +freedom when choosing tools during development and make sure packages created +using different technologies can interoperate without the need for custom +installation procedures. + +This shift became even more clear when PEP 621 was also approved, as a +standardised way of specifying project metadata and dependencies. + +validate-pyproject was born in this context, with the mission of validating +pyproject.toml files, and make sure they are compliant with the standards and +PEPs. Behind the scenes, validate-pyproject relies on JSON Schema files, which, +in turn, are also a standardised way of checking if a given data structure +complies with a certain specification. + +WWW: https://github.com/abravalheri/validate-pyproject