www/py-dj42-django-modelcluster: Add py-dj42-django-modelcluster 6.2.…

…1 (copied from py-django-modelcluster)

django-modelcluster extends Django's foreign key relations to make this
possible. It introduces a new type of relation, ParentalKey, where the related
models are stored locally to the 'parent' model until the parent is explicitly
saved. Up to that point, the related models can still be accessed through a
subset of the QuerySet API.

www/Makefile

@@ -1507,6 +1507,7 @@
     SUBDIR += py-dj42-django-graphiql-debug-toolbar
     SUBDIR += py-dj42-django-guardian
     SUBDIR += py-dj42-django-js-asset
+    SUBDIR += py-dj42-django-modelcluster
     SUBDIR += py-dj42-django-mptt
     SUBDIR += py-dj42-django-multiselectfield
     SUBDIR += py-dj42-django-prometheus

www/py-dj42-django-modelcluster/Makefile

@@ -0,0 +1,27 @@
+PORTNAME=	django-modelcluster
+PORTVERSION=	6.2.1
+CATEGORIES=	www python
+MASTER_SITES=	PYPI
+PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}dj42-
+
+MAINTAINER=	sunpoet@FreeBSD.org
+COMMENT=	Django extension for working with clusters of models as a single unit
+WWW=		https://github.com/wagtail/django-modelcluster
+
+LICENSE=	BSD3CLAUSE
+LICENSE_FILE=	${WRKSRC}/LICENSE
+
+RUN_DEPENDS=	${PYTHON_PKGNAMEPREFIX}django42>=3.2:www/py-django42@${PY_FLAVOR} \
+		${PYTHON_PKGNAMEPREFIX}pytz>=2022.4,1:devel/py-pytz@${PY_FLAVOR}
+
+USES=		python
+USE_PYTHON=	autoplist concurrent distutils
+
+NO_ARCH=	yes
+
+OPTIONS_DEFINE=	TAGGIT
+TAGGIT_DESC=	Tagging support
+
+TAGGIT_RUN_DEPENDS=	${PYTHON_PKGNAMEPREFIX}dj42-django-taggit>=3.1:www/py-dj42-django-taggit@${PY_FLAVOR}
+
+.include <bsd.port.mk>

www/py-dj42-django-modelcluster/distinfo

@@ -0,0 +1,3 @@
+TIMESTAMP = 1708449512
+SHA256 (django-modelcluster-6.2.1.tar.gz) = 3f53d47e1af7aec5e238724be16bbebdac9c518e4788b31429e773dcd8e8ea49
+SIZE (django-modelcluster-6.2.1.tar.gz) = 27121

www/py-dj42-django-modelcluster/pkg-descr

@@ -0,0 +1,5 @@
+django-modelcluster extends Django's foreign key relations to make this
+possible. It introduces a new type of relation, ParentalKey, where the related
+models are stored locally to the 'parent' model until the parent is explicitly
+saved. Up to that point, the related models can still be accessed through a
+subset of the QuerySet API.