| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: perlcritic script |
| Date: | 2018-05-08 20:51:48 |
| Message-ID: | 7551.1525812708@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 5/8/18 13:57, Andrew Dunstan wrote:
>> + # take executable files that file(1) thinks are perl files
>> + find . -type f -perm -100 -exec file {} \; -print |
>> + egrep -i ':.*perl[0-9]*\>' |
> How portable is that?
Well, it's the same code that's in pgperltidy ... but I agree that
it's making a lot of assumptions about the behavior of file(1).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-05-08 21:03:36 | Re: perlcritic script |
| Previous Message | Stas Kelvich | 2018-05-08 20:51:01 | Re: Global snapshots |