Re^3: Perl6 - Module::Build

Test coverage has nothing to do with module installation. However, build systems are for both those who install modules and those who create modules. Otherwise, it might make more sense to call this Module::Install or Module::Create. Since you can't have the former without the latter, why create a build system that only caters to one segment? I am not suggesting that this be one of the first features put in there, but it would be a valuable one.

Test coverage is an important (but neglected) part of ensuring software quality. Any tool that makes it easier to provide better quality software can only help Perl.

Cheers,
Ovid

New address of my CGI Course.

Comment on Re^3: Perl6 - Module::Build

Replies are listed 'Best First'.
Re^4: Perl6 - Module::Build by Corion (Patriarch) on May 27, 2005 at 19:48 UTC
I thought we were talking about the module installer in the top post. Maybe the name "Module::Build" is not well chosen (and Module::Install is a better name but also exists already). I see that test coverage and test running are tightly coupled, but I think that both are best done via Test::Harness and/or `prove` and not within the module installation kit. Otherwise, inclusion of CPAN upload could go in as well, as upload to sourceforge. And an announcement on p5p and/or modules@perl.org ...	[reply]
Re^5: Perl6 - Module::Build by Ovid (Cardinal) on May 27, 2005 at 19:54 UTC
Yes, I think you're right that it should be in Test::Harness or something similar. However, I would like to see readily available hooks available, just as we have `(?:make\|Build) test`. If all dragonchild wants to do is install modules, though, then Module::Build is a bad name. Cheers, Ovid New address of my CGI Course.	[reply]