There is a number of points to address here:
First off, your claim of this being a "bug" in windows comes across to
me as highly arrogant and intentionally insulting. If that was not
your intention, i ask that you please, for the sake of Perl as a
whole, reconsider how you talk to people on OSes that are merely
different than yours.
That said, my concern here is that i run a CPAN Testers Smoker machine
that repeatedly gets stuck trying to make sense of your dist. This
leaves me with two options, both of which are not very desirable.
1: I specialcase your dist with a regex to skip it. Due to the matter
of the beast, this is fragile and can easily stop working or
accidentally cause skipping of dists i didn't want to skip.
Additionally it leaves problems unresolved for other people. As such i
like to reserve this for responsive and irrational authors, which you
don't seem to be.
2: I figure out a way to make CPAN::Reporter send out FAILs for such
dists, which will be a considerable effort, that i'm unsure of being
accepted happily by some authors.
However: There is a third path. You could help ALL automated systems
recognize what systems are supported or not. Frankly: If the colons in
the filenames are the only thing preventing it from working on other
systems, you could probably easily fix that and expand your user
circle. Nevertheless, you could at least pack up the data for testing
in a tarball and only unpack it on systems where Makefile.PL believes
it could work. The CPAN Testers FAQ describes how to set up your
Makefile.PL to appropiately communicate this:
http://wiki.cpantesters.org/wiki/CPANAuthorNotes
Would you be willing to make these changes?
RT for rt.cpan.org