that is hard to patch for opaque structs in newer OpenSSL/LibreSSL.
While this port has been patched to _build_ against current postgresql
it hasn't been patched to _run_ with a newer version since 2018 (11.x)
so seems unlikely to really be used; this has no longer been maintained
upstream for even longer so I intend to remove the port soon.
all consumers were packaged and installed on amd64 by me; all python2
syntax in consumers appears to have been updated at this point making
it possible to move to the 4.x series.
lang/ghc bits look ok to gnezdo@
ok sthen@ on the rest
pgadmin3 is unsupported upstream and doesn't officially support
postgresql above 9.5, but pgadmin4 is a whole different monster, so keep
this one on life support. Tested against 10.5.
(note that there's a 1.22.2 release upstream)
Patch taken from https://bugs.debian.org/878295
ok sthen@ pea@ (MAINTAINER), also tested by Stefan Wollny
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
