Changeset View
Changeset View
Standalone View
Standalone View
devel/py-gitpython/Makefile
| # $FreeBSD$ | # $FreeBSD$ | ||||
| PORTNAME= GitPython | PORTNAME= GitPython | ||||
| PORTVERSION= 1.0.1 | DISTVERSION= 2.1.7 | ||||
| CATEGORIES= devel python | CATEGORIES= devel python | ||||
| MASTER_SITES= CHEESESHOP | MASTER_SITES= CHEESESHOP | ||||
| PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} | PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} | ||||
| MAINTAINER= che@bein.link | MAINTAINER= che@bein.link | ||||
| COMMENT= Python Git Library | COMMENT= Python Git Library | ||||
| LICENSE= BSD3CLAUSE | LICENSE= BSD3CLAUSE | ||||
| LICENSE_FILE= ${WRKSRC}/LICENSE | LICENSE_FILE= ${WRKSRC}/LICENSE | ||||
| RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}gitdb>=0.6.4:devel/py-gitdb | RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}ddt>=1.1.1:devel/py-ddt \ | ||||
| TEST_DEPENDS= ${PYTHON_PKGNAMEPREFIX}nose>=0:devel/py-nose \ | ${PYTHON_PKGNAMEPREFIX}gitdb2>=2.0.0:devel/py-gitdb2\ | ||||
| ${PYTHON_PKGNAMEPREFIX}mock>=0:devel/py-mock \ | ${PYTHON_PKGNAMEPREFIX}unittest2>=0:devel/py-unittest2 | ||||
sunpoet: According to requirements.txt, unittest2 is required for python 2.6 or below. | |||||
| ${PYTHON_PKGNAMEPREFIX}gitdb>=0.6.4:devel/py-gitdb | TEST_DEPENDS= ${PYTHON_PKGNAMEPREFIX}mock>=0:devel/py-mock \ | ||||
| ${PYTHON_PKGNAMEPREFIX}nose>=0:devel/py-nose | |||||
| USES= python | USES= python | ||||
| USE_PYTHON= autoplist distutils | USE_PYTHON= autoplist distutils | ||||
Not Done Inline ActionsIt's good to add USE_PYTHON=concurrent which allows installing this port with different python versions at the same time. sunpoet: It's good to add USE_PYTHON=concurrent which allows installing this port with different python… | |||||
Not Done Inline ActionsI knew about the "concurrent" feature but as I know (and use) very little about python, I was not sure if/when I should use or not. Is it considered a good practice to add concurrent by default to python related ports? rigoletto: I knew about the "concurrent" feature but as I know (and use) very little about python, I was… | |||||
| regression-test: build | regression-test: build | ||||
sunpoetUnsubmitted Done Inline ActionsUse do-test: instead. sunpoet: Use do-test: instead. | |||||
sunpoetUnsubmitted Not Done Inline ActionsSorry for not being clear enough. sunpoet: Sorry for not being clear enough.
I meant to replace the whole line with "do-test:" since it is… | |||||
rigolettoAuthorUnsubmitted Not Done Inline ActionsI thought of that but I could not find a reference of the use of "build" in "regression-test:" or "do-test:" I kept it. rigoletto: I thought of that but I could not find a reference of the use of "build" in "regression-test:"… | |||||
| cd ${WRKSRC} && ${PYTHON_CMD} -m nose | cd ${WRKSRC} && ${PYTHON_CMD} -m nose | ||||
| .include <bsd.port.mk> | .include <bsd.port.mk> | ||||
According to requirements.txt, unittest2 is required for python 2.6 or below.