How to tell CPAN-testers a module is just for a specific platform?

I've written a module that is much like File::Find, but specific for
Win32, using Windows API calls through Win32::API, to loop through the
directories. It's worth the trouble, it can be 2 to 5 times faster than
plain File::Find.

I was considering the name File::Find::Win32 -- in fact, that's the name
I've been using for my own use for many months now. Is this OK?

Now how do I tell CPAN-testers that this module is *only* intended for
Win32? Like Win32::API, where most of the entries for CPAN-testers are
"NA". At first sight I see nothing special in the Makefile.PL or any
other top level file. So, how does it work? Why do CPAN-testers skip
this module?

--
Bart.

Bart Lateur wrote:
> I've written a module that is much like File::Find, but specific for
> Win32, using Windows API calls through Win32::API, to loop through the
> directories. It's worth the trouble, it can be 2 to 5 times faster than
> plain File::Find.
>
> I was considering the name File::Find::Win32 -- in fact, that's the name
> I've been using for my own use for many months now. Is this OK?

Usual thing for Win32-specific modules is to put the 'Win32' first,
especially if the module accesses Windows API functions - so I'm
thinking more along the lines of 'Win32::File::Find'.

>
> Now how do I tell CPAN-testers that this module is *only* intended for
> Win32? Like Win32::API, where most of the entries for CPAN-testers are
> "NA". At first sight I see nothing special in the Makefile.PL or any
> other top level file. So, how does it work? Why do CPAN-testers skip
> this module?
>

My guess is that the testers assume that any module containing the term
'Win32' is for Win32 platform only.

Cheers,
Rob



--
To reply by email u have to take out the u in kalinaubears.

Sisyphus wrote:
> Bart Lateur wrote:
>
[snip] 
>
> My guess is that the testers assume that any module containing the term
> 'Win32' is for Win32 platform only.
>
Rob:  That can't be correct -- although I don't know what *is*.  If you
look at the CPAN testers results on a number of distributions in the
Win32::* namespace, you see at least 3 different kinds of outcomes.

1.  Very well behaved distros where testers reports return 'NA' on
non-Win32 systems.  This is the case Bart described above for Win32::API
and for Win32::OLE (which was originally written by Microsoft).

2.  Distros that test *and PASS* on many systems other than Win32
(implying nothing Win32-specific within).  Examples:  Win32::Exe,
Win32::AbsPath.

3.  Distros that return 'UNKNOWN' for non-Win32 systems at
testers.cpan.org.  Example:  Win32::ASP.  (This could simply be a less
elegant version of case #1.)

Could the answer be in the XS code in case #1?  Perhaps, but I don't
know enough about that to say.  Perhaps Bart could contact Jan Dubois at
ActiveState or cross-post this question on the perl-win32-users list
maintained by ActiveState.

Jim Keenan

Also sprach Bart Lateur:

> I've written a module that is much like File::Find, but specific for
> Win32, using Windows API calls through Win32::API, to loop through the
> directories. It's worth the trouble, it can be 2 to 5 times faster than
> plain File::Find.
>
> I was considering the name File::Find::Win32 -- in fact, that's the name
> I've been using for my own use for many months now. Is this OK?
>
> Now how do I tell CPAN-testers that this module is *only* intended for
> Win32? Like Win32::API, where most of the entries for CPAN-testers are
> "NA". At first sight I see nothing special in the Makefile.PL or any
> other top level file. So, how does it work? Why do CPAN-testers skip
> this module?

I think all you need to do is have your Makefile.PL die when it
detects an unsuitable environment. At least that's what I do in a few of
my modules and I see a couple of NA results. I'd be quite surprised if
they'd exist due to the thoughfulness of some CPAN testers who manually
edited their reports.

Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
 pam{rekcahbus})(rekcah{lrePbus})(lreP{re
htonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval

Jim Keenan wrote:
> Sisyphus wrote:
> 
> [snip]
> 
> Rob:  That can't be correct

Heh .... looks like I must have guessed badly (who would've thought that
possible :-).

Are cpan testers really that naive ???

Cheers,
Rob

--
To reply by email u have to take out the u in kalinaubears.

[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]

In article <q9rsl0ddn8mpqcoq1oripi5pv2n6c6or92@4ax.com>, Bart Lateur
<bart.lateur@pandora.be> wrote:

> Now how do I tell CPAN-testers that this module is *only* intended for
> Win32?

the individual testers seem to have their own set-ups.

You could but a line in the top of the tests that skips all the
tests if they aren't on the right platform (or you could bail
out of all of the tests).

--
brian d foy, comdog@panix.com