net-mgmt/netbox: Create Django 4.0 consumers

* Django 3.2 is currently the "default" version in the ports tree due
  its long term support until April 2024.  Thus ports that are assigned
  to that version will exist until then.

  The following ports are required to make the upgrade of
  net-mgmt/netbox to the 3.2 release possible because it requires Django
  4.0.

  All of the ports listed below were created on the basis of their
  respective original ports:

  - devel/py-dj40-django-rq
  - devel/py-dj40-graphene-django

www/py-django32: Switch consumers over to Django 3.2

Django 2.2 became End-of-Life on 11th April 2022 and Django 3.2 is the
new LTS (= Long Term Support) release which will be supported until
April 2024.

* Switch the most ports that use www/py-django22 to www/py-django32

* Switch www/seahub over to www/py-djangorestframework

* Ports that are not yet ready for Django 3.2 (only three so far) or
  those that have already been set with an expiration date were not
  taken into account.

* Bump PORTREVISION due dependency change where necessary.

PR:		261313
Reviewed by:	bofh, dvl, koobs, ultima
Approved by:	bofh, dvl, koobs, ultima, sunpoet, Kevin Golding, Ivan Rozhuk,
		Alexander Sieg (maintainers)
		maintainer timeout (remaining maintainers)
Differential Revision:	https://reviews.freebsd.org/D34859

www/py-django-redis: Update to 5.2.0

Changes:	https://github.com/jazzband/django-redis/blob/master/CHANGELOG.rst

www/py-django-redis: Update to 5.1.0

- Update WWW

Changes:	https://github.com/jazzband/django-redis/blob/master/CHANGELOG.rst

*: Create Django 3.2 ports for net-mgmt/netbox

* Django 2.2 is currently the "default" version in the ports tree due
  its long term support until April 2022.  Thus ports that are assigned
  to that version will exist until then.

  The following ports are required to make the upgrade of
  net-mgmt/netbox to the 2.11 release possible because it requires
  Django 3.2.  All of the ports listed below were created on the basis
  of their respective original ports:

  - devel/py-dj32-django-rq
  - www/py-dj32-django-auth-ldap
  - www/py-dj32-django-cacheops (updated to a newer release)
  - www/py-dj32-django-cors-headers

www/py-django-redis: Update to 5.0.0

Changes:	https://github.com/jazzband/django-redis/blob/master/CHANGES.rst

www/py-django-redis: Add CATEGORIES=python

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Create some ports that are assigned to Django 3.1 instead Django 2.2

* Django 2.2 is currently the "default" version in the ports tree due its
  long term support until April 2022.  Thus ports that are assigned to that
  version will exist until then.

  The following ports are required to make the upgrade of net-mgmt/netbox to
  the 2.9 release possible because it requires Django 3.1 and provides no
  backwards compatibility for previous versions of Django.

  - www/py-dj31-django-rq
      (copied from r539662 to use the 2.3.2 release for now)
  - www/py-dj31-django-auth-ldap
  - www/py-dj31-django-cacheops
  - www/py-dj31-django-cors-headers

Update to 4.12.1

Changes:	https://github.com/jazzband/django-redis/releases
		https://github.com/jazzband/django-redis/blob/master/CHANGES.rst

Update to 4.11.0

- Update RUN_DEPENDS: use Django 2.2
- Mark www/py-dj22-django-redis as DEPRECATED
- Update www/py-django-prometheus:
  - Change RUN_DEPENDS from py-dj22-django-redis to py-django-redis
  - Bump PORTREVISION for dependency change

Changes:	https://github.com/jazzband/django-redis/releases
		https://github.com/jazzband/django-redis/blob/master/CHANGES.rst
PR:		245522
Submitted by:	kai

Add comment for PORTSCOUT

Fix TEST_DEPENDS: py-fakeredis support was removed

Add PORTSCOUT

Remove build from prerequisite of do-test:

The framework (Mk/bsd.port.mk) already handles it via SEQ.

Remove dependency on the django metaport

With hat:	portmgr

Update version requirement of RUN_DEPENDS

- Take maintainership

Drop a bunch of Python ports which were primarily used for Pootle.

www/py-django-redis: update to 4.10.0

Reported by:	portscout

Use PY_FLAVOR for dependencies.

FLAVOR is the current port's flavor, it should not be used outside of
this scope.

Sponsored by:	Absolight

Move devel/py-msgpack-python to devel/py-msgpack

- Update to 0.5.6
- Update pkg-descr
- Update WWW

Changes:	https://github.com/msgpack/msgpack-python/blob/master/ChangeLog.rst

Fix WWW

Approved by:	portmgr (blanket)

Use the Django meta-port for my Django port to avoid conflicts between them.

Bump PORTREVISIONs

www/py-django-redis: update to 4.9.0

Reported by:	portscout

Convert Python ports to FLAVORS.

  Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the

www/py-django-redis: update to 4.8.0

Submitted by:	portscout

www/py-django-redis: update to 4.7.0

Reported by:	portscout

- update to 4.6.0
- add TEST target

Reported by:	portscout

www/py-django-redis: update to 4.5.0, update WWW

www/py-django-redis: update to 4.4.4

- Add LICENSE_FILE

Approved by:	portmgr blanket

www/py-django-redis: update to 4.4.3 for Pootle 2.7.5

www/py-django-redis: take maintainership, set NO_ARCH

- Reset MAINTAINERship due to fatal email bounces (no MX record, no A record),
maintainer timeouts

Reported by:	portscout

Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z.

With hat:	portmgr
Sponsored by:	Absolight

- Switch forgotten ports over to py-django18
- Fix PYTHON_PKGNAMEPREFIX

Reported by:    antoinebot

- Switch all ports to www/py-django18
- Bump PORTREVISION

- Convert USE_PYTHON to new USES in www/

With hat:	python@

[NEW] www/py-django-redis: Full featured Redis cache/session backend for Django

Django-redis is a BSD Licensed, full featured Redis cache/session
backend for Django.

Why use django-redis?

 * Modular client system (pluggable clients).
 * Master-Slave support in the default client.
 * Used in production in several projects as cache and session storage.
 * Supports infinite timeouts.
 * Python 3 support in same code base.
 * Facilities for raw access to Redis client/connection pool.
 * Highly configurable (can emulate memcached exception behavior, for
   example).
 * Unix sockets supported by default.
 * Pluggable parsers.

WWW: http://niwibe.github.io/django-redis

PR:		191281
Submitted by:	melvyn at magemana dot nl (with minor changes)