| non port: databases/py-django-transaction-hooks/Makefile |
|
SVNWeb
|
Number of commits found: 10 |
|
Thu, 2 Apr 2020
|
[ 00:05 wen  ]  
- Mark DEPRECATED
|
|
Fri, 8 Mar 2019
|
[ 14:45 antoine ] (Only the first 10 of 18 ports in this commit are shown above.  )
Remove dependency on the django metaport
With hat: portmgr
|
|
Sun, 14 Oct 2018
|
[ 15:38 rene ]
Hand over databases/py-django-transaction-hooks to the Python team.
|
|
Wed, 20 Jun 2018
|
[ 17:05 mat ] (Only the first 10 of 1617 ports in this commit are shown above. )
Use PY_FLAVOR for dependencies.
FLAVOR is the current port's flavor, it should not be used outside of
this scope.
Sponsored by: Absolight
|
|
Tue, 6 Mar 2018
|
[ 22:45 rene ]
Use the Django meta-port for my Django port to avoid conflicts between them.
Bump PORTREVISIONs
|
|
Thu, 30 Nov 2017
|
[ 15:50 mat ] (Only the first 10 of 2423 ports in this commit are shown above. )
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 )
|
|
Fri, 1 Apr 2016
|
[ 14:00 mat ] (Only the first 10 of 5103 ports in this commit are shown above. )
Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.
With hat: portmgr
Sponsored by: Absolight
|
|
Sat, 16 Jan 2016
|
[ 11:19 miwi ] (Only the first 10 of 41 ports in this commit are shown above. )
- Switch forgotten ports over to py-django18
- Fix PYTHON_PKGNAMEPREFIX
Reported by: antoinebot
|
|
Fri, 25 Dec 2015
|
[ 07:04 sunpoet ]
- Update MAINTAINER: use @FreeBSD.org
|
|
Tue, 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 |
As an Amazon Associate I earn from qualifying purchases.