On 9/14/07, Paul Johnson <[EMAIL PROTECTED]> wrote: > On Thu, Sep 13, 2007 at 05:10:36PM -0500, brian d foy wrote: > > > Without getting into a bikeshed discussion, I'm looking for prior art > > to test a tarball against a list of local perls before I write my own > > thing. This sounds like a fun and mostly easy project, but I don't want > > to reinvent the wheel. > > > > I want to take a distro tarball and test it against every perl I have > > installed. This is development testing, not end user / installation > > testing: > > > > % test_with_every_perl foo-1.1.tgz > > Testing with perl5.6.2..... > > Testing with perl5.8.0..... > > .... > > Testing with perl5.9.5..... > > > > At the end I get a nice report saying what went wrong with each version. > > > > This is something that I want to run right in my sandbox. The process > > is really easy: unpack the distro, use the appropriate perl with > > Makefile.Pl, and capture the results to make the report. So, who's > > already done this? :) > > http://pjcj.sytes.net/svnweb/Devel::Cover/view/Devel-Cover/trunk/all_versions > is what I use to do this. > > $ perl all_versions make test > > You'd need to change the commands at the end to do exactly what you > wanted - unpacking the tarball rather than deleting the cover_db > directory, I expect. And I have all the perls on my path, which might > not be your case. > > Not sure whether piping the output into a file counts as a nice report > though :-)
Wonder how many of us have hand rolled such scripts... I know i have one, but alas on a machine that is offline right now. Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
