Re: Postgres perl module namespace

Mark Dilger <mark.dilger@enterprisedb.com>

From: Mark Dilger <mark.dilger@enterprisedb.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-11T02:13:17Z
Lists: pgsql-hackers

> On Aug 10, 2021, at 7:11 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> 
> If we were publishing them on CPAN that would be reasonable. But we're
> not, nor are we likely to, I believe.

I'm now trying to understand the purpose of the renaming.  I thought the problem was that RPM packagers wanted something that was unlikely to collide.  Publishing on CPAN would be the way to claim the namespace.

What's the purpose of this idea then?  If there isn't one, I'd rather just keep the current names.

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






Commits

  1. Fix PostgreSQL::Test aliasing for Perl v5.10.1.

  2. For PostgreSQL::Test compatibility, alias entire package symbol tables.

  3. Make PostgresNode easily subclassable