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

22 lines
479 B
Makefile
Raw Normal View History

Pure Python All code, at first, is written in pure Python so that py-postgresql will work anywhere that you can install Python 3. Optimizations in C are made where needed, but are always optional. Prepared Statements Using the PG-API interface, protocol-level prepared statements may be created and used multiple times. db.prepare(sql)(*args) COPY Support Use the convenient COPY interface to directly copy data from one connection to another. No intermediate files or tricks are necessary. Arrays and Composite Typescw Arrays and composites are fully supported. Queries requesting them will returns objects that provide access to the elements within. "pg_python" Quick Console Get a Python console with a connection to PostgreSQL for quick tests and simple scripts. WWW: http://python.projects.postgresql.org/ PR: ports/137782 Submitted by: Volodymyr Kostyrko <c.kworr@gmail.com>
2009-12-18 20:22:02 +01:00
# $FreeBSD$
PORTNAME= postgresql
- update to 1.1.0 - trim Makefile header completely (requested by maintainer) - add CHEESESHOP and make it primary MASTER_SITE, because other locations doesn't hold the new release yet - remove one distfile mirror (requested by maintainer) - add LICENSE (BSD) - replace USE_XZ with USE_ZIP, since it was changed upstream - tune PYDISTUTILS_PKGNAME - move python32 plist stuff into separate file changelog: http://pgfoundry.org/pipermail/python-general/2012-October/001003.html PR: 172544 (but I can't see it in GNATS because of hub transition) Submitted by: rm (myself) Approved by: Volodymyr Kostyrko <c.kworr at gmail dot com> (maintainer, by mail)
2012-10-10 14:20:32 +02:00
PORTVERSION= 1.1.0
Switch default python3 version from 3.3 to 3.4. Bump PORTREVISIONs for the affected ports. Exp-run by: antoine
2015-01-11 00:15:27 +01:00
PORTREVISION= 3
Pure Python All code, at first, is written in pure Python so that py-postgresql will work anywhere that you can install Python 3. Optimizations in C are made where needed, but are always optional. Prepared Statements Using the PG-API interface, protocol-level prepared statements may be created and used multiple times. db.prepare(sql)(*args) COPY Support Use the convenient COPY interface to directly copy data from one connection to another. No intermediate files or tricks are necessary. Arrays and Composite Typescw Arrays and composites are fully supported. Queries requesting them will returns objects that provide access to the elements within. "pg_python" Quick Console Get a Python console with a connection to PostgreSQL for quick tests and simple scripts. WWW: http://python.projects.postgresql.org/ PR: ports/137782 Submitted by: Volodymyr Kostyrko <c.kworr@gmail.com>
2009-12-18 20:22:02 +01:00
CATEGORIES= databases python
- update to 1.1.0 - trim Makefile header completely (requested by maintainer) - add CHEESESHOP and make it primary MASTER_SITE, because other locations doesn't hold the new release yet - remove one distfile mirror (requested by maintainer) - add LICENSE (BSD) - replace USE_XZ with USE_ZIP, since it was changed upstream - tune PYDISTUTILS_PKGNAME - move python32 plist stuff into separate file changelog: http://pgfoundry.org/pipermail/python-general/2012-October/001003.html PR: 172544 (but I can't see it in GNATS because of hub transition) Submitted by: rm (myself) Approved by: Volodymyr Kostyrko <c.kworr at gmail dot com> (maintainer, by mail)
2012-10-10 14:20:32 +02:00
MASTER_SITES= CHEESESHOP \
http://python.projects.postgresql.org/files/
Pure Python All code, at first, is written in pure Python so that py-postgresql will work anywhere that you can install Python 3. Optimizations in C are made where needed, but are always optional. Prepared Statements Using the PG-API interface, protocol-level prepared statements may be created and used multiple times. db.prepare(sql)(*args) COPY Support Use the convenient COPY interface to directly copy data from one connection to another. No intermediate files or tricks are necessary. Arrays and Composite Typescw Arrays and composites are fully supported. Queries requesting them will returns objects that provide access to the elements within. "pg_python" Quick Console Get a Python console with a connection to PostgreSQL for quick tests and simple scripts. WWW: http://python.projects.postgresql.org/ PR: ports/137782 Submitted by: Volodymyr Kostyrko <c.kworr@gmail.com>
2009-12-18 20:22:02 +01:00
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
DISTNAME= py-${PORTNAME}-${PORTVERSION}
DIST_SUBDIR= postgresql
MAINTAINER= c.kworr@gmail.com
COMMENT= Python 3 compatible PostgreSQL database driver and tools
databases/py-postgresql: remove local plist hack and support staging - clarify the license (BSD3C) - use 3 in USE_PYTHON - convert to using auto-generated packing list and remove NO_STAGE - remove local plist hack - it is now handled by bsd.python.mk - bump PORTREVISION for the case Approved by: portmgr (blanket)
2014-03-03 12:09:52 +01:00
LICENSE= BSD3CLAUSE
- update to 1.1.0 - trim Makefile header completely (requested by maintainer) - add CHEESESHOP and make it primary MASTER_SITE, because other locations doesn't hold the new release yet - remove one distfile mirror (requested by maintainer) - add LICENSE (BSD) - replace USE_XZ with USE_ZIP, since it was changed upstream - tune PYDISTUTILS_PKGNAME - move python32 plist stuff into separate file changelog: http://pgfoundry.org/pipermail/python-general/2012-October/001003.html PR: 172544 (but I can't see it in GNATS because of hub transition) Submitted by: rm (myself) Approved by: Volodymyr Kostyrko <c.kworr at gmail dot com> (maintainer, by mail)
2012-10-10 14:20:32 +02:00
databases/py-postgresql: Support python 3.4 When python 3 only is specified, building the port tries to install python 3.3 even if python 3.4 is requested, so this change addresses that. PR: 194656 Submitted by: Axel Rau (chaos1.de) Approved by: maintainer timeout
2014-11-28 11:02:20 +01:00
USES= zip pgsql python:3.3+
Convert USES=pgsql and USES=python:3
2014-10-08 19:14:51 +02:00
USE_PYTHON= distutils autoplist
Pure Python All code, at first, is written in pure Python so that py-postgresql will work anywhere that you can install Python 3. Optimizations in C are made where needed, but are always optional. Prepared Statements Using the PG-API interface, protocol-level prepared statements may be created and used multiple times. db.prepare(sql)(*args) COPY Support Use the convenient COPY interface to directly copy data from one connection to another. No intermediate files or tricks are necessary. Arrays and Composite Typescw Arrays and composites are fully supported. Queries requesting them will returns objects that provide access to the elements within. "pg_python" Quick Console Get a Python console with a connection to PostgreSQL for quick tests and simple scripts. WWW: http://python.projects.postgresql.org/ PR: ports/137782 Submitted by: Volodymyr Kostyrko <c.kworr@gmail.com>
2009-12-18 20:22:02 +01:00
databases/py-postgresql: remove local plist hack and support staging - clarify the license (BSD3C) - use 3 in USE_PYTHON - convert to using auto-generated packing list and remove NO_STAGE - remove local plist hack - it is now handled by bsd.python.mk - bump PORTREVISION for the case Approved by: portmgr (blanket)
2014-03-03 12:09:52 +01:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink