]> granicus.if.org Git - postgresql/commitdiff
perltidy: Don't write backup files
authorPeter Eisentraut <peter_e@gmx.net>
Wed, 21 Mar 2018 14:09:37 +0000 (10:09 -0400)
committerPeter Eisentraut <peter_e@gmx.net>
Fri, 27 Apr 2018 15:37:43 +0000 (11:37 -0400)
Newer perltidy versions can just avoid writing backup files, so we don't
need the old dance of deleting them afterwards.  Supported since 20120619.

https://metacpan.org/source/SHANCOCK/Perl-Tidy-20120619/CHANGES#L61

src/tools/pgindent/perltidyrc
src/tools/pgindent/pgperltidy

index e8ae7c5d8b5d8fe9ed3672c4095f6b0434e2e21c..802b5df37b46ea9b17c26ee1411e1a4f9f40aa47 100644 (file)
@@ -1,5 +1,6 @@
 --add-whitespace
 --backup-and-modify-in-place
+--backup-file-extension=/
 --delete-old-whitespace
 --entab-leading-whitespace=4
 --keep-old-blank-lines=2
index 6098e18428ed19af0ab2dfb012b14b2710919bf0..5d9aa7c64cdd5877a8133b1a5351ce604042b235 100755 (executable)
@@ -18,6 +18,3 @@ PERLTIDY=${PERLTIDY:-perltidy}
 ) |
 sort -u |
 xargs $PERLTIDY --profile=src/tools/pgindent/perltidyrc
-
-# perltidyrc specifies --backup-and-modify-in-place, so get rid of .bak files
-find . -type f -name '*.bak' | xargs rm