> On Aug 10, 2021, at 7:11 PM, Andrew Dunstan <and...@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
- Re: Postgres perl module namespace Andrew Dunstan
- Re: Postgres perl module namespace Tom Lane
- Re: Postgres perl module namespace Andrew Dunstan
- Re: Postgres perl module namespace Michael Paquier
- Re: Postgres perl module namespace Andrew Dunstan
- Re: Postgres perl module namespace Alvaro Herrera
- Re: Postgres perl module namespace Mark Dilger
- Re: Postgres perl module namespace Julien Rouhaud
- Re: Postgres perl module namespace Andrew Dunstan
- Re: Postgres perl module namespace Mark Dilger
- Re: Postgres perl module namespace Andrew Dunstan
- Re: Postgres perl module namespace Andrew Dunstan
- Re: Postgres perl module namespace Alvaro Herrera
- Re: Postgres perl module namespace Tom Lane
- Re: Postgres perl module namespace Andrew Dunstan
- Re: Postgres perl module namespa... Robert Haas
- Re: Postgres perl module nam... Michael Paquier
- Re: Postgres perl module nam... Robert Haas
- Re: Postgres perl module nam... Noah Misch
- Re: Postgres perl module nam... Michael Paquier