Re: perltidy version - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: perltidy version
Date
Msg-id 20180423155841.cx477dennozacjwb@alvherre.pgsql
Whole thread Raw
In response to Re: perltidy version  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: perltidy version
List pgsql-hackers
Peter Eisentraut wrote:
> On 3/5/18 09:02, Magnus Hagander wrote:
> >     I think we should just pick some recent one and use it for X years; use
> >     that one for all backbranches.  I propose X=3.  I propose 20170521
> >     (newer ones seem to cater for stuff that I think we mostly don't use).
> > 
> > 20140328 seems to cover *most* versions. Another argument for that one
> > would be it's the one that we have on Borka, which is where we build the
> > official release tarballs, so we can use that as a stable fallback.
> > 
> > Those are both fairly weak arguments though. As long as we have good
> > instructions for how to make a local install of it that doesn't affect
> > the rest of the system, then that should not matter. And we need such
> > instructions anyway, since it won't be on every distribution. 
> 
> Did we decide on this?

No agreement yet apparently :-)

I still vote we use 20170521 which is recent enough that we won't have
to change it in a few years.

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

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: perltidy version
Next
From: Alvaro Herrera
Date:
Subject: Re: Make description of heap records more talkative for flags