django-tables2 simplifies the task of turning sets of data into HTML tables.
It has native support for pagination and sorting, does for HTML tables what
django.forms does for HTML forms.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py311-django-tables2 listed in the above command, you can pick from the names under the Packages section.
===> The following configuration options are available for py311-django-tables2-2.8.0_1:
TABLIB=off: Enable support for exporting table datasets
===> Use 'make config' to modify these settings
*: Switch consumers over to Django 5.2
Django 4.2 reached its End-of-Life on 7th April 2026 and Django 5.2 is
the new LTS (= Long Term Support) release which will be supported until
April 2028.
* Switch most ports that use www/py-django42 to www/py-django52.
* Where necessary, remove PORTSCOUT, which is no longer needed because
an update to a newer version that no longer supports Django 4.2 should
now be possible.
* Bump PORTREVISION due dependency change where necessary.
PR: 291707
Reviewed by: sunpoet (python)
Differential Revision: https://reviews.freebsd.org/D56966
*: Revise USES=python:... version range constraints
and strip all lower bounds of 3.9 or 3.10 because they are implied now.
python:3.9-X -> python:-X
python:3.9+ -> python
python:3.10-X -> python:-X
python:3.10+ -> python
(options such as ,build preserved)
www/py-django-tables2: Update to 2.7.5
* Support for Python 3.8 was dropped with the 2.7.1 release, adjust
USES=python accordingly.
* Switch to the PEP517 build framework.
Changelog since 2.7.0:
https://github.com/jieter/django-tables2/blob/v2.7.5/CHANGELOG.md
*: Switch consumers over to Django 4.2
Django 3.2 reached its End-of-Life on 1st April 2024 and Django 4.2 is
the new LTS (= Long Term Support) release which will be supported until
April 2026.
* Switch most ports that use www/py-django32 to www/py-django42.
* Ports that are not compatible with Django 3.2 have already been set
with an expiration date were not taken into account.
* Bump PORTREVISION due dependency change where necessary.
PR: 276319
Reviewed by: dvl, grembo, ultima
Approved by: bofh (implicit), dvl, grembo, Kevin Golding, sunpoet,
ultima, maintainer timeout (remaining maintainers)
Differential Revision: https://reviews.freebsd.org/D44637
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
www: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
*
* <hvo.pm@xs4all.nl>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron LI <aly@aaronly.me>
* Aaron Zauner <az_mail@gmx.at>
* Abel Chow <achow@transoft.net>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
* Adrian Steinmann <ast@marabu.ch>
* Akinori MUSHA aka knu <knu@idaemons.org>
(Only the first 15 lines of the commit message are shown above )
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
(Only the first 15 lines of the commit message are shown above )
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
*: 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
(Only the first 15 lines of the commit message are shown above )
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
(Only the first 15 lines of the commit message are shown above )
www/py-django-tables2: Update to 2.3.1
* Add option TABLIB to reflect the optional dependencies as noted via
setup.py. Also set the option as non-default for now because it pulls in
a large set of dependencies and the port runs fine without them.
* Remove stale CONFLICT_INSTALLS entry.
Changelog:
https://github.com/jieter/django-tables2/blob/v2.3.1/CHANGELOG.md
www/py-django-tables2: Assign to Django 2.2
* Because Django 1.11 is End-of-Life since April 2020 thus switch over to
Django 2.2 which is the current LTS release.
* Set the minimum required Python version for Django 2.2 accordingly and
bump PORTREVISION for changed dependencies.
* Mark the repo-copied port www/py-dj22-django-tables2 as DEPRECATED because
it's obsolete now. Don't set an expiration date yet as it's still used by
net-mgmt/netbox and a few more Django 1.11 ports need to be assigned to
Django 2.2 first.
* Also update the CONFLICTS_INSTALL entries as the repo-copied port
py-dj21-django-tables no longer exists in the Ports tree.
PR: 245309
net-mgmt/netbox: Update to 2.5.12 and switch to Django 2.2
Upstream decided to switch from Django 2.1 to the 2.2 LTS release to fix a
rather annoying bug that generated intermittent errors when objects were
deleted/manipulated.
Therefore the same procedure must be done in almost the same way as in
r492690 to make NetBox compatible with Django 2.2 in the ports tree.
That means to repocopy the required Django 1.11 ports, assign them to
Django 2.2, limit them to Python 3.5+ and update all related
CONFLICTS_INSTALL entries accordingly:
* www/py-dj22-django-cors-headers [1]
* www/py-dj22-django-debug-toolbar
(Only the first 15 lines of the commit message are shown above )
www/py-django-tables2: Update to 2.0.6
Notable changes since 1.21.2:
* Fixed issue with wrong time format for TimeColumn.
* Improvements in packaging and publishing helper scripts reducing the
package size considerably.
* Appearance of the paginators might be different from the current 1.x
templates.
* Removed the template argument to the table constructor, use template_name
instead.
* Stopped adding column names to the class attribute of table cells
(<td> tags) by default.
* "verbose_names" derived from model fields are not passed through "title()"
anymore, only the first character is converted to upper case. This follows
Django's convention for verbose field names: "The convention is not to
capitalize the first letter of the verbose_name. Django will automatically
capitalize the first letter where it needs to."
* Many other bugfixes, for a full changelog see here:
https://github.com/jieter/django-tables2/blob/v2.0.6/CHANGELOG.md
Approved by: mentors (implicit)
Create some ports that are assigned to Django 2.1 instead Django 1.11.
Django 1.11 is currently the "default" version in the ports tree due its
long term support until April 2020 thus ports that are assigned to that
version will exist until then.
The following packages are required to make the upgrade of net-mgmt/netbox
to 2.5.x possible because upstream has decided to switch from Django 1.11
to Django 2.1:
* www/py-dj21-django-cors-headers
* www/py-dj21-django-debug-toolbar
* www/py-dj21-django-filter
* www/py-dj21-django-js-asset
* www/py-dj21-django-mptt
(Only the first 15 lines of the commit message are shown above )
Change my maintainer email address to my new one at the FreeBSD project.
Reviewed by: miwi (mentor)
Approved by: miwi (mentor)
Differential Revision: https://reviews.freebsd.org/D19050
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
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
(Only the first 15 lines of the commit message are shown above )
- Allow ports to work with any django version avaliable.
- Allow staging and use AUTOPLIST option for www/py-django-tables2
PR: ports/184147
Submitted by: Kozlov Sergey <kozlov.sergey.404@gmail.com> (maintainer)
www/django-tables2: Table/data-grid framework for Django
django-tables2 simplifies the task of turning sets of data into HTML tables.
It has native support for pagination and sorting, does for HTML tables what
django.forms does for HTML forms.
WWW: https://github.com/bradleyayers/django-tables2/
PR: ports/181899
Submitted by: Kozlov Sergey <kozlov.sergey.404 gmail.com> (maintainer)
