Re: [Module-build-general] Ready for 0.19?

[<ajs...@ya...>]

Ken Williams <ke...@ma...> wrote:
> I've released a new beta, 0.18_04, to cpan and sourceforge.  It gets
> the 'install_base' parameter working, completing the design document
> I posted here a few days ago.  I'd love it if people could test it
> out, by either/both of running the regression tests & using it to
> test/install their own Module::Build-using modules.
>
> If it looks good, I'll make the 0.19 release.

Still passes OK on Windows.

Just a random thought. I noticed t/compat.t contains:
  skip_test("Don't know how to invoke 'make'") unless $Config{make};
which is good. But what if $Config{make} points to something that
is not there? (I fear some Windows users may have $Config{make}
set to 'nmake' yet not have nmake installed).

Given that Module::Build does not depend on make, I think it would
be nice if compat.t could check if $Config{make} was indeed
available on the PATH and skip the tests if not -- instead of
failing, as it currently does. Does anyone know of a clean,
portable way to tell if a command is available on the PATH?
If not, a simple workaround is to start compat.t with the test:
  $Config{make} force_do_it
Remember, force_do_it is a dummy target that does nothing, so this
command should always succeed with a return code of zero ... unless
$Config{make} is indeed unavailable.

/-\


http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.