Bug#834213: perlcritic: some code causes a perltidy.ERR file to be created or overwritten

[Paul Wise]

On Sat, 2016-08-20 at 17:37 +0200, Salvatore Bonaccorso wrote:

> I think perlcritic/perltidy is behaving here as documented.

I see, thanks for the pointers.

It seems like it would be possible to override the default using two
configuration files and one option to perlcritic, that has the downside
of disabling the users' own perlcritic/perltidy configuration files.
I also don't really want check-all-the-things to add many overrides
for other tools before they work in a safe-by-default way.

> One can argue that the default value is not a safe one, and rather
> pertidy should by default should use -se, and only if overwritten to
> write to a somefile.pl.ERR.

I agree that the default is not safe and should be changed.

> But if so, this would need to be changed upstream, and not diverged in
> the Debian packaging.

Would it be possible for you to forward the bug report upstream?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20160821/31e04b71/attachment.sig>