Hello, Stephen Adkins wrote:
I initially wrote App::Build to solve exactly the problem you describe.
[...]
However, Mattia Barbon picked it up and continues to develop it for Module::Build 0.28xx.
Indeed, I think I can already contribute to that with a few tweaks, as I've been trying to use it in my current project.
P.S. App::Options is an awesome/awesomely simple configuration/option handling module. It would be too bad if Module::Build::ConfigData didn't work well with App::Options.
Although App::Options might be very useful mightn't it be made optional? I've nothing against using App::Options, except App::Build assumes you're going to use it and disables the generation of the ConfigData.pm module by overriding has_config_data() to always return false.
I suspect App::Build probably shouldn't clobber ConfigData.pm like that, as that mechanism is still perfectly good and removing it makes porting a module from Module::Build more difficult. From what I can see, with a few small changes they could co-exist without any problem.
In fact, perhaps anything App::Build does to change the default behaviour of Module::Build methods are probably pitfalls for the unwary Module::Build porter which might also be better as optional features? (A specific example of this is that rscan_dir() is overridden to exclude SVS/RCS/.svn directories.)
Anyway, I'll contact Mattia about this. Cheers, Nick
