Re: perltidy version

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: perltidy version
Date: 2018-04-23 23:57:58
Message-ID: 20180423235758.GC1570@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 23, 2018 at 12:40:00PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>> I still vote we use 20170521 which is recent enough that we won't have
>> to change it in a few years.

That's the version available on Debian sid, so from the prospective of
any Debian user this is a handy version to use when sending patches:
perltidy/unstable,now 20170521-1 all [installed]

>> I further vote that we change the URL in pgindent/README from
>> sourceforge to metacpan.org,
>> https://metacpan.org/pod/distribution/Perl-Tidy/lib/Perl/Tidy.pod
>
> I have no particular opinion on which version to use, but if we're going
> to change for this cycle, it's time to do so. I'm intending to do the
> initial pgindent run pretty soon ...

I would vote for using a newer version with v11.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2018-04-23 23:59:34 Re: Built-in connection pooling
Previous Message Michael Paquier 2018-04-23 23:52:17 Re: Problem while setting the fpw with SIGHUP