Hi!

I'm the new upstream for all OSSP software, please cf.
  https://lists.sr.ht/~nabijaczleweli/ossp/%3Cdas6vdk2hnazoi6b3wf5bbctpcqnqfky2nmdcwco7lkv2drmpk@tarta.nabijaczleweli.xyz%3E

Due to its continued use downstream, I have thawed out ossp-uuid,
and over the past few days brought it up to date to modern standards at
  https://git.sr.ht/~nabijaczleweli/ossp-uuid

The bindings were in an even sorrier state than the main library,
with C++ getting fully deprecated and PHP killed outright.
This leaves the PostgreSQL binding, which I see at
  https://www.postgresql.org/docs/16/uuid-ossp.html
is... part of postgres now,
and can be configured without using the upstream library?

Upstream ships an extension that targets postgres 8
(obviously doesn't build in /any/ capacity against postgres 15).

You have done more upstream-equivalent maintenance on this extension
than anyone else, so ‒ would I be right to kill ossp-uuid/pgsql
and update the BINDINGS list to point at the URL for the plugin
(if so, which one's the best one)?

Prospective ossp-uuid 1.6.3/1.7.0 also implements generation of v6/v7 UUIDs,
and distinguishes the Max special value like the Nil one.
AIUI RFC 9562, v6 and Max may be of particular interest to database users.
Max at least is quite simple:
  Datum
  uuid_max(PG_FUNCTION_ARGS)
  {
  #ifdef HAVE_UUID_OSSP
  	return special_uuid_value("max");
  #else
  	return uuid_generate_internal(0, NULL,
  								  "ffffffff-ffff-ffff-ffff-ffffffffffff", 36);
  #endif
  }
but I don't see a strict counterpart to v6 and v7 in the other back-ends,
so the cost/benefit of this is unclear to me at this time
(though I expect it to be clearer to you).

At any rate, the link that currently points to
http://www.ossp.org/pkg/lib/uuid/ should be updated to point to either
the new upstream or the archive.

Best,
наб