Re: Perl6 - Module::Build

[Ovid]

Great news! Thanks. In no particular order:

• Support for .buildrc so commonly used build requirements don't need to be respecified every time.
• Finer granularity on requirements: required, required for build, required if a particular feature is requested, required for tests, recommended, etc.
• Built in support for test coverage and code profiling (when such is available).
• Uninstall (should probably keep a database of installation history, too).

[Corion]

What does test coverage have to do with module installation?

[Ovid]

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.

[Corion]

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 [e-mail] ...

[PodMaster]

Well, users need to run tests, and developers shouldn't be encouraged to break TEST_VERBOSE=1 .... the less developers have to invent, the more useful cpan-tester results become

update: what I'm trying to say is that everyone needs a good uniform experience from the start, so they can focus on more important things