saintmike has asked for the wisdom of the Perl Monks concerning the following question:
Only problem is that some things are meant to be broken, and I don't want to get email to tell me that they are. For example, some modules just don't work on Windows because of OS limitations. What am I as the CPAN author supposed to do about it?
If I mark the tests as "SKIPPED" on these platforms, the smoke tests will show up as PASS and module consumers might be tricked into thinking that it's OK to use the module on the broken platform.
On the other hand, if I don't do anything about it, I look somewhat foolish with my broken tests and keep getting emails from the smokers.
Is there a way to say "This is not supposed to be working, don't use it on this platform"?