freebsd-ports/www/py-django-evolution/Makefile

# Created by: Li-Wen Hsu <lwhsu@FreeBSD.org>
# $FreeBSD$

PORTNAME=	django-evolution
PORTVERSION=	0.7.7
PORTREVISION=	1
DISTVERSIONPREFIX=	release-
CATEGORIES=	www python
PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}

MAINTAINER=	cs@FreeBSD.org
COMMENT=	Database schema evolution tool for the Django web framework

LICENSE=	BSD3CLAUSE

RUN_DEPENDS=	${PYTHON_SITELIBDIR}/django/bin/django-admin.py:www/py-django111@${PY_FLAVOR}

USE_GITHUB=	yes

GH_ACCOUNT=	beanbaginc
USES=		python:2.7
USE_PYTHON=	distutils autoplist

post-extract:
	${RM} -r ${WRKSRC}/tests

.include <bsd.port.mk>
- Switch dependency to www/py-django Since py-django-evolution is only required by www/reviewboard, and the latest version of reviewboard now depends on django-1.4.x , switch the dependency port of py-django-evolution to avoid conflict. - Pass maintainership to submitter PR: ports/175093 Submitted by: Po-Chien Lin <linpc@cs.nctu.edu.tw> 2013-01-07 10:52:04 +01:00			`# Created by: Li-Wen Hsu <lwhsu@FreeBSD.org>`
Add py-django-evolution 0.6.2, a database schema evolution tool for the Django web framework. 2011-02-26 15:50:11 +01:00			`# $FreeBSD$`

			`PORTNAME= django-evolution`
Update to 0.7.7 2018-04-30 20:37:27 +02:00			`PORTVERSION= 0.7.7`
- Switch to py-django111 - Bump PORTREVISION Sponsored by: iXsystems Inc. 2018-05-10 17:02:43 +02:00			`PORTREVISION= 1`
Don't use GH_TAGNAME when it can be created with DISTVERSION* variables. Sponsored by: Absolight 2015-12-28 15:42:50 +01:00			`DISTVERSIONPREFIX= release-`
Add py-django-evolution 0.6.2, a database schema evolution tool for the Django web framework. 2011-02-26 15:50:11 +01:00			`CATEGORIES= www python`
			`PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}`

- Update to 0.7.6 - Compatible with newer django versions now - Move to Github - Take maintainership 2015-12-25 23:01:42 +01:00			`MAINTAINER= cs@FreeBSD.org`
Remove indefinite articles and trailing periods from COMMENT, plus minor COMMENT typos and surrounding whitespace fixes. A few Makefiles where not included as they contain Latin-1 characters that break the Phabricator workflow. Category W. CR: D510 Approved by: portmgr (bapt) 2014-08-06 11:11:57 +02:00			`COMMENT= Database schema evolution tool for the Django web framework`
Add py-django-evolution 0.6.2, a database schema evolution tool for the Django web framework. 2011-02-26 15:50:11 +01:00
Update "BSD" license in www category 2014-12-21 17:09:04 +01:00			`LICENSE= BSD3CLAUSE`
Add py-django-evolution 0.6.2, a database schema evolution tool for the Django web framework. 2011-02-26 15:50:11 +01:00
Use PY_FLAVOR for dependencies. FLAVOR is the current port's flavor, it should not be used outside of this scope. Sponsored by: Absolight 2018-06-20 19:05:41 +02:00			`RUN_DEPENDS= ${PYTHON_SITELIBDIR}/django/bin/django-admin.py:www/py-django111@${PY_FLAVOR}`
- Update to 0.6.5 2011-09-14 00:58:34 +02:00
- Update to 0.7.6 - Compatible with newer django versions now - Move to Github - Take maintainership 2015-12-25 23:01:42 +01:00			`USE_GITHUB= yes`

			`GH_ACCOUNT= beanbaginc`
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 2017-11-30 16:50:30 +01:00			`USES= python:2.7`
- Convert USE_PYTHON to new USES in www/ With hat: python@ 2015-01-03 09:41:20 +01:00			`USE_PYTHON= distutils autoplist`
Add py-django-evolution 0.6.2, a database schema evolution tool for the Django web framework. 2011-02-26 15:50:11 +01:00
- Add a workaround to fix conflicts with tests/__init__.py Reported by: antoine 2014-06-28 22:29:43 +02:00			`post-extract:`
			`${RM} -r ${WRKSRC}/tests`

Add py-django-evolution 0.6.2, a database schema evolution tool for the Django web framework. 2011-02-26 15:50:11 +01:00			`.include <bsd.port.mk>`