non port: www/py-django-overextends/Makefile |
Number of commits found: 16 |
Monday, 29 Jun 2020
|
16:17 sunpoet
Mark DEPRECATED and set EXPIRATION_DATE to 2020-07-15
PR: 247590
Submitted by: kai
|
Friday, 8 Mar 2019
|
14:45 antoine
Remove dependency on the django metaport
With hat: portmgr
|
Saturday, 19 Jan 2019
|
20:41 sunpoet
Add LICENSE_FILE
- Take maintainership
|
16:48 rene
Drop a bunch of Python ports which were primarily used for Pootle.
|
Wednesday, 20 Jun 2018
|
17:05 mat
Use PY_FLAVOR for dependencies.
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight
|
Tuesday, 6 Mar 2018
|
22:45 rene
Use the Django meta-port for my Django port to avoid conflicts between them.
Bump PORTREVISIONs
|
Thursday, 30 Nov 2017
|
15:50 mat
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
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
|
Tuesday, 11 Apr 2017
|
18:24 rene
www/py-django-overextends: update to 0.4.3
Submitted by: portscout
|
Sunday, 21 Aug 2016
|
00:18 rene
www/py-django-overextends: update to 0.4.2 (updates supported Django versions)
|
Wednesday, 27 Apr 2016
|
18:22 rene
www/py-django-overextends: add dependency on textproc/py-sphinx-me, found
while testing an update to textproc/pootle
Bump PORTREVISION
|
Friday, 1 Apr 2016
|
14:33 mat
Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z.
With hat: portmgr
Sponsored by: Absolight
|
Saturday, 16 Jan 2016
|
11:19 miwi
- Switch forgotten ports over to py-django18
- Fix PYTHON_PKGNAMEPREFIX
Reported by: antoinebot
|
09:52 miwi
- Switch all ports to www/py-django18
- Bump PORTREVISION
|
Friday, 25 Dec 2015
|
07:04 sunpoet
- Update MAINTAINER: use @FreeBSD.org
|
Monday, 21 Dec 2015
|
18:57 rene
www/py-django-overextends: update to 0.4.1
This release adds support for Django 1.9
|
Monday, 23 Nov 2015
|
21:10 rene
A Django reusable app providing the overextends template tag, a drop-in
replacement for Django's extends tag, which allows you to use circular
template inheritance.
The primary use-case for overextends is to simultaneously override and extend
templates from other reusable apps, in your own Django project.
WWW: https://github.com/stephenmcd/django-overextends
|
Number of commits found: 16 |