non port: databases/py-django-transaction-hooks/Makefile |
Number of commits found: 10 |
Thursday, 2 Apr 2020
|
00:05 wen
- Mark DEPRECATED
|
Friday, 8 Mar 2019
|
14:45 antoine
Remove dependency on the django metaport
With hat: portmgr
|
Sunday, 14 Oct 2018
|
15:38 rene
Hand over databases/py-django-transaction-hooks to the Python team.
|
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
|
Friday, 1 Apr 2016
|
14:00 mat
Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.
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
|
Friday, 25 Dec 2015
|
07:04 sunpoet
- Update MAINTAINER: use @FreeBSD.org
|
Tuesday, 8 Dec 2015
|
20:21 rene
A better alternative to the native transaction signals of Django.
Sometimes you need to fire off an action related to the current database
transaction, but only if the transaction successfully commits. Examples:
a Celery task, an email notification, or a cache invalidation.
Doing this correctly while accounting for savepoints that might be
individually rolled back, closed/dropped connections, and idiosyncrasies of
various databases, is non-trivial. Transaction signals just make it easier
to do it wrong.
django-transaction-hooks does the heavy lifting so you don't have to.
WWW: https://github.com/arljm/django-transaction-hooks/
|
Number of commits found: 10 |