Skip Menu |

This queue is for tickets about the Pod-LaTeX CPAN distribution.

Report information
The Basics
Id: 83385
Status: open
Priority: 0/
Queue: Pod-LaTeX

People
Owner: Nobody in particular
Requestors: dagolden [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: pod2latex.PL not strict compliant
In testing the viability of a "strict by default" perl, I noticed that pod2latex.PL is not strict compliant in its first stanza. Because it is used to build the standard Perl library, it stands in the way of building a strict perl to test how the rest of the core can handle strictures. It is listed as "undef" upstream, so will be patched in blead. You may wish to synchronize it back to CPAN, or to explicitly declare upstream to be blead, in which case the Perl 5 Porters will take responsibility for a dual-life release to CPAN after the next blead release.
Subject: Re: [rt.cpan.org #83385] pod2latex.PL not strict compliant
Date: Sun, 17 Feb 2013 20:47:53 -0700
To: bug-Pod-LaTeX [...] rt.cpan.org
From: Tim Jenness <tjenness [...] cpan.org>
It is upstream CPAN and Pod::LaTeX is marked to be removed from core in 5.20 because there was no champion to port it to Pod::Simple and it was felt that latex doesn't need to be in the core perl anyhow. On Sat, Feb 16, 2013 at 6:06 PM, David Golden via RT < bug-Pod-LaTeX@rt.cpan.org> wrote: Show quoted text
> Sat Feb 16 20:06:22 2013: Request 83385 was acted upon. > Transaction: Ticket created by DAGOLDEN > Queue: Pod-LaTeX > Subject: pod2latex.PL not strict compliant > Broken in: (no value) > Severity: Normal > Owner: Nobody > Requestors: dagolden@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=83385 > > > > In testing the viability of a "strict by default" perl, I noticed that > pod2latex.PL is not strict compliant in its first stanza. Because it is > used to build the standard Perl library, it stands in the way of > building a strict perl to test how the rest of the core can handle > strictures. > > It is listed as "undef" upstream, so will be patched in blead. You may > wish to synchronize it back to CPAN, or to explicitly declare upstream > to be blead, in which case the Perl 5 Porters will take responsibility > for a dual-life release to CPAN after the next blead release. > >