Horton

Re: perltidy version

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Tels" <nospam-pg-abuse@bloodgate.com>
Cc: "Michael Paquier" <michael@paquier.xyz>, "Alvaro Herrera" <alvherre@alvh.no-ip.org>, "Peter Eisentraut" <peter.eisentraut@2ndquadrant.com>, "Magnus Hagander" <magnus@hagander.net>, "Dagfinn Ilmari Mannsåker" <ilmari@ilmari.org>, "PostgreSQL-development" <pgsql-hackers@postgresql.org>
Date: 2018-04-25T20:12:16Z
Lists: pgsql-hackers 
"Tels" <nospam-pg-abuse@bloodgate.com> writes:
> On Wed, April 25, 2018 12:35 pm, Tom Lane wrote:
>> Agreed on pointing to cpan, but that page is pretty confusing if you're
>> looking for a non-bleeding-edge version.  I suggest linking to
>> https://cpan.metacpan.org/authors/id/S/SH/SHANCOCK/
>> which presents a handy directory listing.

> Linking to the author directory can be pretty confusing, because if a new
> (co-)-maintainer releases something, it will end up not in this directory.

As long as we're pointing at a specific past release, this seems like not
much of a problem.  Also, if I understood correctly, we need to expose
the author name as part of the install-with-cpan recipe, so taking it
out of the other URL seems like little advantage.

			regards, tom lane

Commits

  1. Reindent Perl files with perltidy version 20170521.

  2. Change pgindent/README to specify that we use perltidy version 20170521.