Date: Wed, 11 Aug 2021 09:22:45 -0400
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>,
	Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Postgres perl module namespace
Message-ID: <202108111322.cj455y35dc2c@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <9b9f5c7b-fccf-b2a5-a288-b413941bd766@dunslane.net>
Archived-At: 
 <https://www.postgresql.org/message-id/202108111322.cj455y35dc2c%40alvherre.pgsql>
Precedence: bulk

On 2021-Aug-10, Andrew Dunstan wrote:

> If we were publishing them on CPAN that would be reasonable. But we're
> not, nor are we likely to, I believe. I'd rather not have to add two
> level of directory hierarchy for this, and this also seems a bit
> long-winded:
> 
>     my $node = PostgreSQL::Test::Cluster->new('nodename');

I'll recast my vote to make this line be

     my $node = PgTest::Cluster->new('nodename');

which seems succint enough.  I could get behind PgTest::PgCluster too,
but having a second Pg there seems unnecessary.

-- 
Álvaro Herrera              Valdivia, Chile  —  https://www.EnterpriseDB.com/
"Cada quien es cada cual y baja las escaleras como quiere" (JMSerrat)