PyGreSQL is a python module that interfaces to a PostgreSQL database. It embeds
the PostgreSQL query library to allow easy use of the powerful PostgreSQL
features from a Python script.
PyGreSQL includes a DB-API 2.0 compliant API wrapper.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py311-PyGreSQL listed in the above command, you can pick from the names under the Packages section.
===> The following configuration options are available for py311-PyGreSQL-6.0_1,1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal
Any missed ports, feel free to bump.
Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Relax hardcoded paths to fix build with Python 3.8.7
Since r558913 Python 3.8 incorporates BPO-42604 [1] which changed the
shared libs naming scheme. This means "EXT_SUFFIX" is now derived from
SOABI and yields with Python 3.8 to ".cpython-38.so" instead of ".so".
The affected ports strip the libaries in the "post-install" target via
hardcoded path(s) and the build fails at the end because the new extension
is not expected at this place.
Remedy the issue by adding wildcards to these paths. This should also
prepare the ports for future Python releases, which will use the new shared
libs naming scheme.
[1] https://bugs.python.org/issue42604
PR: 252057
Reported by: John Kennedy
Reviewed by: fluffy, koobs
Approved by: koobs (python)
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
- install port documentation into stagedir uncoditionally and remove inclusion
of bsd.port.options.mk
- unmute docs installation command
- remove no more needed patch
- bump PORTREVISION
- Convert to PYDISTUTILS_AUTOPLIST
- Enable stage support
- Limit to the supported python versions
- Change to new LIB_DEPENDS where necessary
- Switch to new OPTIONS framework where necessary
- update to 4.1
- trim Makefile header
- update MASTER_SITES
- remove indefinite article from COMMENT
- limit python version to 2.x only
- convert to optionsng (NOPORTDOCS case)
- patch out setuptools for from setup.py for now (mainly to not use
PYEASYINSTALL_OSARCH)
- update formatting in pkg-descr and change tab with space at WWW
Reported by: D'Arcy J.M. Cain <darcy@PyGreSQL.org> (on ports@)
For ports maintained by ports@FreeBSD.org, remove names and/or
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
- Make Python 2.5.1 the default Python version
- Add significantly better support in bsd.python.mk for working with
Python Eggs and the easy_install system
Tested by: pointyhat runs
Approved by: pav (portmgr)
Most work by: perky
Thanks to: pav
Split the postgresql ports into a server and a client part.
All ports depending on postgresql shall use the USE_PGSQL=yes knob
defined in Mk/bsd.ports.mk. Bumping portrevisions where needed.
PR: 75344
Approved by: portmgr@ (kris), ade & sean (mentors)
Update PyGreSQL to 3.4. Previous version was packed with the
postgresql dist, and while postgresql was version 7.3.5, PyGreSQL's
own version just bumped from 3.3 to 3.4. Hence portepoch.
PR: ports/61597
Submitted by: Palle Girgensohn <girgen@pingpong.net> (maintainer)
Update py-PyGreSQL to version 7.3
This patch really only takes over maintainership from
ports@freebsd.org. Since I manage most of the postgresql
ports, I might as well take this one too, I guess?
I have verified that it builds with postgresql-7.3
PR: ports/45887
Submitted by: Palle Girgensohn <girgen@pingpong.net>
- Make this port a subport of databases/postgresql7, since the development of
PyGreSQL has been folded into that of PostgreSQL itself.
- This update effectivly takes PyGreSQL to version 3.3, which is distributed
with PostgreSQL 7.2.3.
- Byte-compile installed modules to ensure clean deinstallation.
- Install documentation under $DOCSDIR.
- Remove Makefile from $FILESDIR - not required anymore.
- Remove patch-pgdb.py - not required any longer.
- Add two patches to ensure installation is $PREFIX-clean.
- Update pkg-comment and pkg-descr to reflect the current status of the port.
PostGreSQL 7.1 can install in two places, either ${PREFIX} (hier(7)) or
${PREFIX}/pgsql (old layout). Adjust compiler flags so that headers and
libraries are found in either case.
