kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/textproc/py-pyPEG2/Makefile

21 lines
410 B
Makefile
Raw Normal View History

Add py-pyPEG2. I am currently in the process of creating ports for various components related to CloudABI, including ARPC (an RPC framework that supports file descriptor passing) and Flower (a capability-based network backplane). The former comes with a script called 'aprotoc' for creating C++ bindings for messages and RPC services. This script depends on Python's pyPEG2 package to parse (a subset of) Protobuf's .proto grammar. Reviewed by: wg Differential Revision: https://reviews.freebsd.org/D12048
2017-08-17 11:45:13 +02:00
# Created by: Ed Schouten <ed@FreeBSD.org>
# $FreeBSD$
PORTNAME= pyPEG2
PORTVERSION= 2.15.2
CATEGORIES= textproc python
MASTER_SITES= CHEESESHOP
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
MAINTAINER= ed@FreeBSD.org
COMMENT= Parsing Expression Grammar (PEG) parser for Python
LICENSE= GPLv2+
LICENSE_FILE= ${WRKSRC}/LICENSE.txt
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
Add py-pyPEG2. I am currently in the process of creating ports for various components related to CloudABI, including ARPC (an RPC framework that supports file descriptor passing) and Flower (a capability-based network backplane). The former comes with a script called 'aprotoc' for creating C++ bindings for messages and RPC services. This script depends on Python's pyPEG2 package to parse (a subset of) Protobuf's .proto grammar. Reviewed by: wg Differential Revision: https://reviews.freebsd.org/D12048
2017-08-17 11:45:13 +02:00
USE_PYTHON= autoplist distutils
NO_ARCH= yes
.include <bsd.port.mk>
Reference in a new issue Copy permalink