pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Postgres perl module namespace
Date: Tue, 10 Aug 2021 22:33:50 -0400
Message-ID: <b0331ef7-ae71-6a8a-2e5f-5d46c97a6e35@dunslane.net> (raw)
In-Reply-To: <6c33f6e2-659e-04d3-36cd-ec7c94450712@dunslane.net>
References: <aede93a4-7d92-ef26-398f-5094944c2504@dunslane.net>
	<3796296.1621545509@sss.pgh.pa.us>
	<1290c0d8-f619-0fa2-7c2f-8077ad967bbc@dunslane.net>
	<EEF22566-8BDA-4CBB-94C6-6E31ED66BF60@enterprisedb.com>
	<9b9f5c7b-fccf-b2a5-a288-b413941bd766@dunslane.net>
	<3792F74B-4190-4E55-A4C6-6A18E2226505@enterprisedb.com>
	<6c33f6e2-659e-04d3-36cd-ec7c94450712@dunslane.net>


On 8/10/21 10:26 PM, Andrew Dunstan wrote:
> On 8/10/21 10:13 PM, Mark Dilger wrote:
>>> 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.
>
>
> Yes we want them to be in a namespace where they are unlikely to collide
> with anything else. No, you don't have to publish on CPAN to achieve that.
>

Incidentally, not publishing on CPAN was a major reason given a few
years ago for using fairly lax perlcritic policies. If we publish these
on CPAN now some people at least might want to revisit that decision.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com






view thread (63+ messages)  latest in thread

Message-ID: <b0331ef7-ae71-6a8a-2e5f-5d46c97a6e35@dunslane.net>
Permalink:  ../b0331ef7-ae71-6a8a-2e5f-5d46c97a6e35@dunslane.net/
Also on:    postgresql.org/message-id/b0331ef7-ae71-6a8a-2e5f-5d46c97a6e35@dunslane.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: andrew@dunslane.net, mark.dilger@enterprisedb.com, tgl@sss.pgh.pa.us, pgsql-hackers@lists.postgresql.org
  Subject: Re: Postgres perl module namespace
  In-Reply-To: <b0331ef7-ae71-6a8a-2e5f-5d46c97a6e35@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox