Bug#742004: perltidy.LOG file left behind

[Steven Hancock]

Don,
I'll look into this and try to make a general fix.  I'll try to get it by
next week and will let you know.
Thanks,
Steve


On Tue, Mar 18, 2014 at 4:53 PM, Don Armstrong <don at donarmstrong.com> wrote:

> Steve: bringing you in on this; it appears perltidy now creates a
> perltidy.LOG file, which causes a few problems in Debian; see
> https://bugs.debian.org/742004 for the full saga.
>
> On Tue, 18 Mar 2014, Russ Allbery wrote:
> > I looked into this further. The problem is that Perl::Tidy now always
> > attempts to create a log file in the current directory unless told to
> > create it elsewhere with the logfile parameter to its constructor.
> > (There doesn't seem to be a way to tell it not to create the thing,
> > although maybe you can point it to /dev/null.) Perl::Critic's policy
> > for running Perl::Tidy doesn't pass that parameter or provide any way
> > for the caller to pass it.
>
> Perltidy really shouldn't be creating a logfile unless you tell it to
> create a logfile.
>
> I'm OK with carrying a local patch in Debian for this in perltidy, but
> I'd like to propose that a logfile not be created unless logstream is
> passed (or some other non-default option.)
>
> Steve: would that be acceptable upstream? Or should I just prepare a
> Debian-local patch for that?
>
> --
> Don Armstrong                      http://www.donarmstrong.com
>
> I would like to be the air
> that inhabits you for a moment
> only. I would like to be that unnoticed
> & that necessary.
>  -- Margaret Atwood "Poetry in Motion" p140
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20140319/a127a6a2/attachment.html>