On Tue, 2 Nov 2004, John Peacock wrote:
Module::Build already has it's own way to tell about dependencies but afaik no one uses it except CPANPLUS.
And what is worse is that the Module::Build dependencies are treated as /suggestions/, and will not throw an error if one is not met. I just got a cpantester's report for one of my modules which only works with Perl 5.8.1 or better. Even though I added 'perl => 5.8.1' to the dependencies, Module::Build happily went on to try and build/test the module on a 5.6.1 machine. I actually have to add 'use 5.8.1' to the top of the Build.PL file to correctly bail out.
Actually, M::B is no different fom EU::MM in this regard. EU::MM will install a module which has unmet dependencies. It's CPAN or CPANPLUS that do the enforcement. If they're not enforcing them properly with M::B modules, that obviously needs to be corrected.
-dave
/*=========================== VegGuide.Org Your guide to all that's veg. ===========================*/
