summaryrefslogtreecommitdiff
path: root/databases/py-django-transaction-hooks (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-07-02Remove expired port:Rene Ladan3-42/+0
2020-07-02 databases/py-django-transaction-hooks: Unmaintained upstream and merged into Django since 1.9 Notes: svn path=/head/; revision=541031
2020-04-02- Mark DEPRECATEDWen Heping1-0/+3
Notes: svn path=/head/; revision=530251
2019-03-08Remove dependency on the django metaportAntoine Brodin1-2/+2
With hat: portmgr Notes: svn path=/head/; revision=495043
2018-10-14Hand over databases/py-django-transaction-hooks to the Python team.Rene Ladan1-1/+1
Notes: svn path=/head/; revision=482046
2018-06-20Use PY_FLAVOR for dependencies.Mathieu Arnold1-1/+1
FLAVOR is the current port's flavor, it should not be used outside of this scope. Sponsored by: Absolight Notes: svn path=/head/; revision=472884
2018-03-06Use the Django meta-port for my Django port to avoid conflicts between them.Rene Ladan1-2/+2
Bump PORTREVISIONs Notes: svn path=/head/; revision=463771
2017-11-30Convert Python ports to FLAVORS.Mathieu Arnold1-1/+1
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 Notes: svn path=/head/; revision=455210
2017-06-25Fix WWWSunpoet Po-Chuan Hsieh1-1/+1
Approved by: portmgr (blanket) Notes: svn path=/head/; revision=444292
2016-04-01Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.Mathieu Arnold1-1/+1
With hat: portmgr Sponsored by: Absolight Notes: svn path=/head/; revision=412346
2016-01-16- Switch forgotten ports over to py-django18Martin Wilke1-1/+2
- Fix PYTHON_PKGNAMEPREFIX Reported by: antoinebot Notes: svn path=/head/; revision=406208
2015-12-25- Update MAINTAINER: use @FreeBSD.orgSunpoet Po-Chuan Hsieh1-1/+1
Notes: svn path=/head/; revision=404403
2015-12-08A better alternative to the native transaction signals of Django.Rene Ladan3-0/+38
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/ Notes: svn path=/head/; revision=403346
generated by cgit v1.2.3 (git 2.25.1) at 2025-11-24 04:37:28 +0000