kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/py-Pyro/Makefile

38 lines
1,001 B
Makefile
Raw Normal View History

Add DESTDIR support.
2008-06-12 04:14:13 +02:00
# $NetBSD: Makefile,v 1.10 2008/06/12 02:14:28 joerg Exp $
Initial import of Pyro from pkgsrc-wip. Pyro is an acronym for PYthon Remote Objects. It is an advanced and powerful Distributed Object Technology system written entirely in Python, that is designed to be very easy to use. It resembles Java's Remote Method Invocation (RMI). It is less similar to CORBA - which is a system- and language independent Distributed Object Technology and has much more to offer than Pyro or RMI. But Pyro is small, simple and free (MIT software license). Get the manual from http://pyro.sourceforge.net/pyro-manual/PyroManual.html Check quite impressive success stories on http://pyro.sourceforge.net/projects.html
2004-12-31 11:13:56 +01:00
#
DISTNAME= Pyro-3.4
PKGNAME= ${PYPKGPREFIX}-${DISTNAME}
Fixed pkglint warnings.
2006-06-17 23:01:29 +02:00
PKGREVISION= 2
Initial import of Pyro from pkgsrc-wip. Pyro is an acronym for PYthon Remote Objects. It is an advanced and powerful Distributed Object Technology system written entirely in Python, that is designed to be very easy to use. It resembles Java's Remote Method Invocation (RMI). It is less similar to CORBA - which is a system- and language independent Distributed Object Technology and has much more to offer than Pyro or RMI. But Pyro is small, simple and free (MIT software license). Get the manual from http://pyro.sourceforge.net/pyro-manual/PyroManual.html Check quite impressive success stories on http://pyro.sourceforge.net/projects.html
2004-12-31 11:13:56 +01:00
CATEGORIES= devel
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=pyro/}
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Initial import of Pyro from pkgsrc-wip. Pyro is an acronym for PYthon Remote Objects. It is an advanced and powerful Distributed Object Technology system written entirely in Python, that is designed to be very easy to use. It resembles Java's Remote Method Invocation (RMI). It is less similar to CORBA - which is a system- and language independent Distributed Object Technology and has much more to offer than Pyro or RMI. But Pyro is small, simple and free (MIT software license). Get the manual from http://pyro.sourceforge.net/pyro-manual/PyroManual.html Check quite impressive success stories on http://pyro.sourceforge.net/projects.html
2004-12-31 11:13:56 +01:00
HOMEPAGE= http://pyro.sourceforge.net/
COMMENT= Distributed Object Technology system in Python
Add DESTDIR support.
2008-06-12 04:14:13 +02:00
PKG_DESTDIR_SUPPORT= user-destdir
Initial import of Pyro from pkgsrc-wip. Pyro is an acronym for PYthon Remote Objects. It is an advanced and powerful Distributed Object Technology system written entirely in Python, that is designed to be very easy to use. It resembles Java's Remote Method Invocation (RMI). It is less similar to CORBA - which is a system- and language independent Distributed Object Technology and has much more to offer than Pyro or RMI. But Pyro is small, simple and free (MIT software license). Get the manual from http://pyro.sourceforge.net/pyro-manual/PyroManual.html Check quite impressive success stories on http://pyro.sourceforge.net/projects.html
2004-12-31 11:13:56 +01:00
PY_PATCHPLIST= yes
PYDISTUTILSPKG= yes
Use PYVERSSUFFIX to differentiate between versions built for different versions of Python and to resolve conflicts with other packages. Bump PKGREVISION.
2005-01-07 17:17:42 +01:00
PLIST_SUBST+= PYVERSSUFFIX="-${PYVERSSUFFIX}"
Fixed pkglint warnings.
2006-06-17 23:01:29 +02:00
MAKE_ENV+= PKGSRC="1"
MAKE_ENV+= PYVERSSUFFIX="-${PYVERSSUFFIX}"
Whitespace police.
2005-01-09 11:53:45 +01:00
Use PYVERSSUFFIX to differentiate between versions built for different versions of Python and to resolve conflicts with other packages. Bump PKGREVISION.
2005-01-07 17:17:42 +01:00
post-extract:
Fixed pkglint warnings.
2006-06-17 23:01:29 +02:00
set -e; \
Use PYVERSSUFFIX to differentiate between versions built for different versions of Python and to resolve conflicts with other packages. Bump PKGREVISION.
2005-01-07 17:17:42 +01:00
cd ${WRKSRC}/bin; \
${MV} es es-${PYVERSSUFFIX}; \
${MV} esd esd-${PYVERSSUFFIX}; \
${MV} genguid genguid-${PYVERSSUFFIX}; \
${MV} ns ns-${PYVERSSUFFIX}; \
${MV} nsc nsc-${PYVERSSUFFIX}; \
${MV} nsd nsd-${PYVERSSUFFIX}; \
${MV} pyroc pyroc-${PYVERSSUFFIX}; \
${MV} rns rns-${PYVERSSUFFIX}; \
${MV} wxnsc wxnsc-${PYVERSSUFFIX}; \
${MV} xnsc xnsc-${PYVERSSUFFIX}
Initial import of Pyro from pkgsrc-wip. Pyro is an acronym for PYthon Remote Objects. It is an advanced and powerful Distributed Object Technology system written entirely in Python, that is designed to be very easy to use. It resembles Java's Remote Method Invocation (RMI). It is less similar to CORBA - which is a system- and language independent Distributed Object Technology and has much more to offer than Pyro or RMI. But Pyro is small, simple and free (MIT software license). Get the manual from http://pyro.sourceforge.net/pyro-manual/PyroManual.html Check quite impressive success stories on http://pyro.sourceforge.net/projects.html
2004-12-31 11:13:56 +01:00
.include "../../lang/python/extension.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink