databases/pglogical: update to 2.4.5

Reported by:	portscout
Changes:	https://github.com/2ndQuadrant/pglogical/releases/tag/REL2_4_5

databases/pglogical: update to 2.4.4

Changes:	https://github.com/2ndQuadrant/pglogical/releases/tag/REL2_4_4
Reported by:	portscout

databases/pglogical: update to 2.4.3

Changes:	https://github.com/2ndQuadrant/pglogical/releases/tag/REL2_4_3
Reported by:	portscout

databases/pglogical: update to 2_4_2

ChangeLog:	https://github.com/2ndQuadrant/pglogical/releases/tag/REL2_4_2

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.

databases: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  "Choe, Cheng-Dae" whitekid
  *  "Mahdi Mokhtari <mokhi64@gmail.com>"
  *  "Meikel Brandmeyer" <ocaml-sqlite3-port@kotka.de>
  *  <hvo.pm@xs4all.nl>
  *  <jsmith@resonatingmedia.com>
  *  <ports@c0decafe.net>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Akinori MUSHA aka knu <knu@idaemons.org>
  *  Alan Snelson <Alan@Wave2.org>

databases/pglogical: update to 2.4.1

Update WWW

ChangeLog:	https://github.com/2ndQuadrant/pglogical/releases/tag/REL2_4_1

databases/pglogical: Add CPE information

Approved by:	portmgr (blanket)

databases/pglogical: update to 2.4.0

ChangeLog:	https://github.com/2ndQuadrant/pglogical/releases

databases/pglogical: Security update to 2.3.4

ChangeLog:	https://github.com/2ndQuadrant/pglogical/releases/tag/REL2_3_4
MFH:		2021Q2

Remove # $FreeBSD$ from Makefiles.

Update to 2.3.3

Release notes: https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

Actually delete the patch file which we are no longer applying.

Update to 2.3.2

Delete support for postgresql-9.4

Delete patch fixed upstream

ChangeLog:   https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

databases/pglogical: fix build on GCC architectures

Use C11 compiler:
pglogical_dependency.c:235: error: static declaration of 'AcquireDeletionLock'
follows non-static declaration
/usr/local/include/postgresql/server/catalog/dependency.h:198: error: previous
declaration of 'AcquireDeletionLock' was here

Fix build after upstream changes in postgres 9.5 -- 12 made functions
AcquireDeletionLock() and ReleaseDeletionLock() extern rather than
static in:

  
https://github.com/postgres/postgres/commit/5be594caf818e0b5e33f8dec191f2707394a6d95

The function definitions in the postgresql sources are identical to
those in the pglogical sources, so let's just link against the
postgresql versions.

postgresql-9.4 is EoL, so didn't receive the same changes in the
latest round of postgresql updates.

While here, fix another of the patches which should no be applied when
compiling against all versions of postgresql.  Plus fix the pkg-plist
-- how did this port ever package previously?

Upgrade to 2.3.1

Release Notes: https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

Update to 2.3.0

Relese Notes:	https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

Update to 2.2.2

ChangeLog:	https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

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

Fix compilation with postgresql11.  With previous versions of
postgresql, <arpa/inet.h> was included automatically as part of the
postgres module building environment.  But it needs to be included
explicitly for the most recent postgres.

Submitted by:	andriy@irbisnet.com

Really update to version 2.2.1

Just updating PORTVERSION won't achieve anything if you don't also
make the corresponding change to GH_TAGNAME.  To avoid this sort of
embarrassment in future, drop PORTVERSION and GH_TAGNAME for the main
distfile in favour of DISTVERSION and DISTVERSIONPREFIX.

Reorder some items in the Makefile to mollify portlint.

Reported by:	mat

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

Update to 2.2.1

After an include, PLIST_SUB must be appended to, not overwritten.

If it is overwritten, many values will be clobbered, and
pain will ensue.

PR:		230864
Submitted by:	mat
exp-runs by:	antoine

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)

Update to 2.2.0

ChangeLog: https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

Update to 2.1.1

Release Notes:	https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

Update to 2.1.0

ChangeLog: https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

Fix build with postgresql9.4

Switch to downloading sources from GitHub, and add the pglogical_dump
submodule.  This was omitted from the tarball provided by 2nd Quadrant
in the latest version.  The pglogical_dump code is only compiled with
postgresql9.4 which failed to build -- using other postgresql versions
worked fine.

Reported by:	pkg-fallout

Update to 2.0.1

Release notes: https://www.2ndquadrant.com/en/resources/pglogical/release-notes/

Update to 2.0.0

ChangeLog:	https://2ndquadrant.com/en/resources/pglogical/release-notes/

Update to 1.2.2

ChangeLog:	https://2ndquadrant.com/en/resources/pglogical/release-notes/

Update to 1.2.1

Changes:  https://github.com/2ndQuadrant/pglogical/compare/REL1_2_1...master

Remove the now pointless pkg-message, forgotten in previous commit.

pglogical: update to 1.2.0
pglogical-output: delete; merged into databases/pglogical

The databases/pglogical	  and databases/pglogical-output ports have been
merged into one codebase upstream, and database/pglogical now installs
the pglogical-output.so module.

pkg(8) should handle the merger	correctly; portmaster(1),
portupgrade(1) users are advised to manually delete pglogical-output
before upgrading.

Install the .sql files for release 1.1.2 -- this is missing from the
release tarball, but has been fixed in upstream's Github.

Add pglogical_dump, pglogical_origin--1.0.0.sql and
pglogical_origin.control conditionally on the postgresql version --
these are only compiled and installed with postgresql-9.4.x

Submitted by:	Anderson Neves <anderson.ufal@gmail.com>

Update to 1.1.2

This fixes an important regression with replication of TOASTed values.

ChangeLog: http://2ndquadrant.com/en/resources/pglogical/release-notes/

pglogical is a logical replication system implemented entirely as a
PostgreSQL extension. Fully integrated, it requires no triggers or
external programs. This alternative to physical replication is a
highly efficient method of replicating data using a publish/subscribe
model for selective replication.

WWW: http://2ndquadrant.com/en/resources/pglogical/