cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
openbsd-ports/devel/py-protocols/Makefile

39 lines
946 B
Makefile
Raw Normal View History

Remove MASTER_SITES=${MASTER_SITE_BACKUP} which is already taken care of by bsd.port.mk
2014-08-30 21:54:07 +00:00
# $OpenBSD: Makefile,v 1.21 2014/08/30 21:54:08 jasper Exp $
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
Remove quotes surrounding COMMENT*/PERMIT_*/BROKEN
2007-09-16 02:52:56 +00:00
COMMENT= protocol definition, declaration and adaptation
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
VERSION= 1.0
rename variable, REVISION has a special meaning now
2010-07-10 20:30:37 +00:00
REV= 2306
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
DISTNAME= PyProtocols
bumpski for python
2010-08-30 22:24:14 +00:00
PKGNAME= py-protocols-${VERSION}r${REV}
normalize pkgpath
2011-09-16 09:24:48 +00:00
REVISION= 0
bump EPOCH to deal with REVISION screwup from last year
2011-06-10 19:35:31 +00:00
EPOCH= 0
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
remove lang/python category from individual ports
2007-12-10 21:07:51 +00:00
CATEGORIES= devel
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
fix homepage, bump pkgname
2008-07-09 12:13:45 +00:00
HOMEPAGE= http://peak.telecommunity.com/PyProtocols.html
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
MAINTAINER= Martynas Venckus <martynas@openbsd.org>
# PSF/ZPL
PERMIT_PACKAGE_CDROM= Yes
rename variable, REVISION has a special meaning now
2010-07-10 20:30:37 +00:00
DISTFILES= PyProtocols-${VERSION}a0dev_r${REV}${EXTRACT_SUFX}
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
MODULES= lang/python
move depends to new style
2010-11-15 19:45:56 +00:00
RUN_DEPENDS= devel/py-decoratortools
Remove MASTER_SITES=${MASTER_SITE_BACKUP} which is already taken care of by bsd.port.mk
2014-08-30 21:54:07 +00:00
TEST_DEPENDS= devel/py-decoratortools
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
MODPY_SETUPTOOLS= Yes
First ports I found which need Add WANTLIB += ${MODPY_WANTLIB}, bump revision. ok sthen@.
2011-05-31 05:44:26 +00:00
WANTLIB += ${MODPY_WANTLIB}
import py-protocols-1.0r2306 PyProtocols extends the PEP 246 adapt() function with a new "declaration API" that lets you easily define your own protocols and adapters, and declare what adapters should be used to adapt what types, objects, or protocols. In addition to its own Interface type, PyProtocols can also use Twisted and Zope's Interface types. "go ahead" (after some nice tweaks, actually) steven@
2007-06-23 21:41:54 +00:00
# make regress happy after fake
post-install:
rm -fr ${WRKSRC}/src/PyProtocols.egg-info
${INSTALL_DATA_DIR} ${PREFIX}/share/doc/py-protocols/ref
${INSTALL_DATA} ${WRKSRC}/docs/ref/*.tex ${PREFIX}/share/doc/py-protocols/ref/
${INSTALL_DATA} ${WRKSRC}/README.txt ${PREFIX}/share/doc/py-protocols/
.include <bsd.port.mk>
Reference in New Issue Copy Permalink