All the Perl that's Practical to Extract and Report
use Perl Log In
barbie (2653)
reversethis-{ku. ... m} {ta} {eibrab}
http://barbie.missbarbell.co.uk/
Leader of Birmingham.pm [pm.org] and a CPAN author [cpan.org]. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [yapc-surveys.org] and the QA Hackathon [qa-hackathon.org] websites. Also the current caretaker for the CPAN Testers websites and data stores.
If you really want to find out more, buy me a Guinness
Links:
Memoirs of a Roadie [missbarbell.co.uk]
[pm.org]
CPAN Testers Reports [cpantesters.org]
YAPC Conference Surveys [yapc-surveys.org]
QA Hackathon [qa-hackathon.org]
Change files for core modules
I was doing some dependency checking yesterday, for some of the distributions that have failed to complete any CPAN testing. I was quite surprised that there are several modules that reference specific versions of core Perl modules. File::Path gets referenced most. So I decided to see why someone would specifically look to a specific version than just the installed core version. The distribution in question was referencing the version in perl-5.8.6.
Unfortunately there isn't a distinct Changes file for File::Path, or if there is, it isn't anywhere that is easily viewable on the web. There are all the perldeltas, but it takes a while to sift through them to see what has changed against a core module.
So my question is there anywhere that the Changes file for just File::Path or any other core module, is viewable on the web?
Next week I will investigate whether that version of File::Path is actually required, or whether the authors just put it in because that was the version on their system. It's a shame that too many distributions insist on being only compatible with Perl 5.8+, when most are quite compatible with Perl 5.6.1 too.
I also noted that Catalyst now depends on Perl 5.8, thus rendering a whole bunch of CPAN distributions N/A for Perl 5.6.1. Maypole works in Perl 5.6.1, so I'm not sure why they've changed to ignore anything before 5.8.
--Larry Wall in stab.c from the perl source code
Why something would need 5.8.4 (Score:1)
The big 5.8 thing in Perl::MinimumVersion is also "use utf8;". So given the diversity of applications it supports, unicode would seem an obvious one.
Hang on a second.... there's a better way of doing this. perlver to the rescue!
adam@red:~/.cpan/build$ perlver Catalyst-5.33/
-------------------------------------------------------------------------
Re:Why something would need 5.8.4 (Score:2)
Funny you should mention Perl::MinimumVersion, as I would liked to have used it. Its another that is on my list with dependency failures. Unfortunately Test::SubCalls is failing the same tests as imacat's report [perl.org], except mine fails on Windows, Perl 5.6.1.
I have been doing the checking by hand previously and noting to the authors that it really does work for 5.6.1, however I had planned to write something that can do that (using Perl::MinimumVersion) to check a distribution as soon as it produces a NA repor
Re:Why something would need 5.8.4 (Score:1)
Re:Why something would need 5.8.4 (Score:2)
That should perhaps feature a bit more prominently in their docs I think.
However, I was only cpan-testing Catalyst and related modules, so manual intervention wasn't the plan. It just means I don't test anything Catalyst dependent anymore.
Reading the fix, I'm more inclined to get frustrated that there isn't an independent release for some core modules, so that those of us who can't upgrade past 5.6.1 can still get the benefit of fixes. If these fixes to Class::Struct work fine on 5.6.1, why is there a de
Changelogs (Score:2)
Re:Changelogs (Score:2)
I guess it's better than nothing, but it still requires a lot of effort to figure out what changes went into which version. There is no mention of the module version being updated in those changes files. This might be acceptable for looking up one module, but once you start trying to look at the differences for other files, it starts to become painful.
Hence why I was hoping there might actually be a Changes file for each individual file. :(
Re:Changelogs (Score:1)
I think that Module::Corelist contains the Perforce revision number for each release. Also, you can use the corelist command to see which version of the module went into each release.
etc.
As for queries by file, the perlbrowse site will let you browse the 50 most