On Fri, Mar 20, 2009 at 7:53 PM, Curtis Jewell
<[email protected]> wrote:
>> I don't think OS Unsupported is the correct response. The OS isn't
>> unsupported, the user is just missing a prereq. I'd do something like
>> this:
If you are missing things in configure_requires, CPAN Testers should
ignore the result. At least CPAN::Reporter does and if CPANPLUS-based
testers, we'll fix that at the hackathon next weekend. :-) So "OS
Unsupported" hackery isn't necessary. (And isn't appropriate anyway,
as you said.)
>> eval { require Win32API::Registry }
>> or die "Can't build without Win32API::Registry";
>> I don't think there's a standard way to say "you're missing a module I
>> need in
>> the configure stage" other than configure_requires.
>
> Thanks. I'll do that. Such is life. And since W32API::Registry isn't a
> pure perl module, I can't do the inc\ thing with it.
For older toolchains that don't understand configure_requires, you
should probably have that kind of eval statement anyway. Or don't and
just let "require Win32API::Registry" blow up with the normal error.
Also -- I think Win32API::Registry comes with Strawberry Perl, so at
least some win32 perls will have it already and on ActiveState, many
people will probably use PPMs instead of Alien anyway.
You might also consider whether you can use a command-line tool to
query instead of requiring a perl module. E.g. a google query gave
me: http://commandwindows.com/reg.htm
Then you wouldn't need Win32API::Registry at all.
-- David
