Front page | perl.perl5.porters |
Postings from January 2016
Re: Pod::Checker
Thread Previous
From:
Steve Hay via perl5-porters
Date:
January 8, 2016 21:59
Subject:
Re: Pod::Checker
Message ID:
CADED=K4EMOig4d9uRBsGCPes4Yu2spzhTV+vDVgc-q2jQNU0uw@mail.gmail.com
On 8 January 2016 at 19:33, Karl Williamson <public@khwilliamson.com> wrote:
> On 01/08/2016 11:44 AM, Steve Hay via perl5-porters wrote:
>>
>> I just tried updating Pod::Checker from 1.60 to 1.71 in blead... All
>> is (superficially) fine apart from t/porting/podcheck.t now failing
>> because Pod::Checker is now derived from Pod::Simple rather than
>> Pod::Parser.
>>
>> It looks like the kind of thing needed to fix it up has already been
>> done, e.g. in
>>
>>
>> http://perl5.git.perl.org/perl.git/commit/7d7a29938b99ea208c6f315a516be7c0070fe552
>>
>> (which also removes Pod::Parser), although just nicking the podcheck.t
>> from there didn't fix it.
>>
>> What is the status of this work? Does this need to land in time for
>> 5.24.0?
>>
>> (I had a quick Google and found that I asked a similar question just
>> over two years ago, which I have to confess was news to me! --
>> http://www.nntp.perl.org/group/perl.perl5.porters/2013/09/msg208074.html)
>>
>
> The status is that it never got completed. I intended to do it during the
> freeze of 5.22 for 5.24, but found higher priority issues. I plan to work
> on it after visible changes freeze is done for 5.24, or if other things come
> up, during the freeze period, so it goes in 5.25. I see no reason for it to
> have to be done in time for 5.24. Maybe a comment should be added to it so
> that people don't keep trying to remove it and find this block after they've
> wasted their efforts.
A comment somewhere suitable isn't a bad idea -- it's quite possible
as 5.24 gets closer that more people may look to see if any module
upgrades can be slipped in in time.
Thread Previous