| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Tels" <nospam-pg-abuse(at)bloodgate(dot)com> |
| Cc: | "Michael Paquier" <michael(at)paquier(dot)xyz>, "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-25 20:12:16 |
| Message-ID: | 20200.1524687136@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Tels" <nospam-pg-abuse(at)bloodgate(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-04-25 20:31:08 | Re: WIP: a way forward on bootstrap data |
| Previous Message | Mark Dilger | 2018-04-25 20:09:25 | Re: WIP: a way forward on bootstrap data |