Jan Dubois wrote:
On Mon, 03 Mar 2008, David Golden wrote:
On Mon, Mar 3, 2008 at 10:25 AM, Jan Dubois <[EMAIL PROTECTED]> wrote:
However, I think using Devel::AssertOS is really overkill for this purpose.
I just use the following code in most Win32::* modules:
unless ($^O eq "MSWin32" || $^O eq "cygwin") {
die "OS unsupported\n";
}
Probably I will switch to this.
However, I was suggested in the past to use Devel::AssertOS
and wanted to give it a try.
I think it's interesting, but what really puzzles me is how
I managed to screw up the META.yml that many times before
understanding that EU::MM was breaking it just before
a `make dist' :(
What is the actual kind-of "state-of-the-art" on this?
I mean EU::MM vs. Module::Build?
I'd like to support as many old systems as possible,
without going into ridiculously old ones (5.005, for example),
and I've had unpleasant experiences myself with first releases
of Module::Build.
The "use-devel-assertos" script is supposed
to be "fire and forget" to hide the details.
I noticed the missing "no_index" on inc, and I tried
to contact David about this.
use Devel::AssertOS qw(MicrosoftWindows MSWin32 Cygwin);
This should have been `use Devel::AssertOS qw(MicrosoftWindows)'.
Anyways, it is of course up to Cosimo to decide how he wants to do
this; I was just pointing out the problems...
I'm thinking of going the simple way and die-ing manually.
Anyway, is it correct that die-ing with "OS unsupported"
then causes cpan-testers "NA" results?
--
Cosimo
