pgpool-II allows multiple PostgreSQL servers (DB nodes) to be
connected, which enables queries to be executed simultaneously on all
servers.
It enables "parallel query" processing. Also, pgpool-II can be started
as pgpool-I by changing configuration parameters. pgpool-II that is
executed in pgpool-I mode enables multiple DB nodes to be connected,
which was not possible in pgpool-I.
WWW: http://www.pgpool.net/
===> The following configuration options are available for pgpool-II33-3.3.22:
DOCS=on: Build and/or install documentation
LIBMEMCACHED=off: Build with MemCached support
PAM=on: Build with PAM support
SSL=on: SSL protocol support
===> Use 'make config' to modify these settings
Remove expired ports:
2018-07-31 net/rubygem-gitaly-proto096: Obsoleted by update of www/gitlab-ce.
Please use net/rubygem-gitaly-proto instead.
2018-07-31 security/tripwire12: unfetchable
2018-07-31 security/rubygem-rbnacl4: Obsoleted by update of www/gitlab-ce.
Please use security/rubygem-rbnacl instead.
2018-07-31 www/rubygem-gon61: Obsoleted by update of www/gitlab-ce. Please use
www/rubygem-gon instead.
2018-07-31 databases/pgpool-II-33: Will be deprecated by upstream, please switch
to newer pgpool versions
2018-07-31 devel/rubygem-grape-entity060: Obsoleted by update of www/gitlab-ce.
Please use devel/rubygem-grape-entity instead.
2018-07-31 net/rubygem-gitaly-proto099: Obsoleted by update of www/gitlab-ce.
Please use net/rubygem-gitaly-proto instead.
2018-07-31 net/rubygem-gitaly-proto095: Obsoleted by update of www/gitlab-ce.
Please use net/rubygem-gitaly-proto instead.
2018-07-31 net/rubygem-omniauth-github11: Obsoleted by update of www/gitlab-ce.
Please use net/rubygem-omniauth-github instead.
2018-07-31 net/rubygem-asset_sync220: Obsoleted by update of www/gitlab-ce.
Please use net/rubygem-asset_sync instead.
2018-07-31 www/rubygem-gollum-lib-gitlab: Obsoleted by update of www/gitlab-ce.
Please use www/rubygem-gitlab-gollum-lib instead.
2018-08-01 www/py-django-threaded-multihost: Project development unmaintained
2018-08-01 www/py-django-keyedcache: Project development abandoned
2018-08-01 www/py-django-signals-ahoy: Project development unmaintained
Workaround the following problem on aarch64 by setting LLD_UNSAFE=yes:
cc: error: invalid linker name in argument '-fuse-ld=bfd'
Neither emaste nor I can figure out exactly where the offending stanza is
coming in. It will take someone with more knowledge of gmake debug flags,
and possibly the src build infrastructure, to figure it out.
While here, pet portlint.
Approved by: portmgr (tier-2 blanket)
databases/pgpool-II-33: Update from 3.3.7 to 3.3.20
While here:
- set EXPIRATION_DATE and mark DEPRECATED because of incoming EOL
- clean up conflicts
- add LIB_DEPENDS when option is set
- regenerate patches with make makepatch
- Remove redundant definitions of IPV6_DESC and [OPEN]SSL_DESC when closely
matching standard ones from `Mk/bsd.options.desc.mk'
- Rename couple of options to standard name or the one that better reflects
their usage
databases/libmemcached: Update to 1.0.18 and much more
- Update to 1.0.18 and pkg-plist accordingly
- Add LICENSE (BSD3CLAUSE) and LICENSE_FILE
- Add TEST_DEPENDS and regression-test target
- Perl is not required, remove USE_PERL and from USES
- Split LDFLAGS from CONFIGURE_ENV, they're already set there
- Add libmemcachedprotocol to CONFIGURE_ARGS (Now default: off)
- Add OPTIONS for hash functions, debug and dtrace
- pkg-descr: Update WWW: URL
- Add patches for:
* alloca.h include not found on FreeBSD
* cinttypes include location
* clang compatibility
- Strip shared libraries manually since upstream install-strip target is
fail
Changes:
https://launchpad.net/libmemcached/+announcements
[1] https://bugs.launchpad.net/libmemcached/+bug/1245562
[2] https://bugs.launchpad.net/libmemcached/+bug/1400560
Approved by: Mikhail Tsatsenko <m.tsatsenko@gmail.com> (maintainer, via email)
New port databases/pgpool-II-33
Repo copy from databases/pgpool-II. Changes from that port:
- New port for pgpool-II33-3.3.3
- Stagify
- Add libtool, gmake, pgsql, perl5 to USES. Drop .la files -- this is a
new port, so there can't be any pre-existing consumers of the .la files
to worry about.
- Use options helpers
- The configure used with this software is buggy and doesn't understand
(Only the first 15 lines of the commit message are shown above )
