Re: Module::BuildX::* vs Module::Build::*

# from Christopher J. Madsen
# on Tuesday 11 March 2008 14:00:

>Does anybody else have an opinion about this?  I don't have strong
>objections to Module::BuildX, but the search-and-replace will be a
> hassle. I'd like a little more consensus that it's worth it.

My concern is that besides 'Module::Build::Platform::*', the 
Module-Build dist already contains these:

  Module::Build::Version
  Module::Build::Config
  Module::Build::ModuleInfo
  Module::Build::Cookbook
  Module::Build::Notes
  Module::Build::Base
  Module::Build::PPMMaker
  Module::Build::PodParser
  Module::Build::Compat
  Module::Build::YAML
  Module::Build::Dumper

Yes, as you mentioned, the precedence is already there:

>>   Module::Build::Convert
>>   Module::Build::Debian
>>   Module::Build::JSAN
>>   Module::Build::Kwalitee
>>   Module::Build::PM_Filter
>>   Module::Build::TestReporter

And unfortunately these are all subclasses, so mixing their 
functionality together will be non-fun.  But then, we've never gotten 
around to creating a plugin system, so there's never really been any 
sort of prescription or recommended practice.  But I guess it's worth 
noting that none of the M::B::* stuff in the M-B dist is a subclass.

--Eric
-- 
hobgoblin n 1: (folklore) a small grotesque supernatural creature that
          makes trouble for human beings
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------