Here's my CPAN goods. [cpan.org]
FAIL Win32-Font-NameToFile-0.10 x86_64-linux-thread-multi-ld 2.6.22.10
FAIL Win32-WebBrowser-1.02 x86_64-linux-thread-multi-ld 2.6.22.10
Yes, I'm shocked, shocked! to learn my Win32 modules failed on 64 bit Linux!
Seriously: I think we can do a better filtering job than this...if for no other reason than running tests for Win32 packages on Linux is a waste of CPANTester resources. How about
if (($filename=~/^Win32/) && ($^O ne 'MSWin32'))
{
next; # NO SOUP FOR YOU!!!
}
You are to blame here... (Score:1)
You are supposed to have your Makefile.PL abort appropriately if you see you are on a platform that you don't support.
There are, in fact, some Win32:: modules that DO run on Linux under certain wine'y scenarios. So a filename-related shortcut wouldn't work.
Your Makefile.PL already says what dependencies and what perl version it needs. It should also abort cleanly if it doesn't support some host.
That way they don't have to gue
Re: (Score:2)
Mea culpa...no soup for me! (Score:1)
But it still bothers me...
Re: (Score:1)
Re: (Score:1)
Re: (Score:1)
"How can I indicate that my distribution only works on a particular operating system?" [grango.org]
Further questions about testing are better asked on the list cpan-testers-discuss [grango.org].
Re: (Score:0)
In which holy book is this documented?
Re: CPAN Testers (Score:2)
Sounds like it might be a job for Devel::AssertOS [cpan.org].
Re: (Score:1)