Re: [Module::Build] Making 0.28 a reality

[David G. <da...@hy...>]

Yitzchak Scott-Thoennes wrote:
> On Mon, Mar 20, 2006 at 11:09:39PM -0500, David Golden wrote:
>> John Peacock wrote:
>>> I'm not Ken (nor do I play him on TV), but I'd actually suggest moving 
>>> the code to a new module Module::Build::YAML, both for clarity (to 
>>> separate the code for easier maintenance) as well as easier replacement 
>>> (M::B can try to use YAML and only if it isn't found switch to using 
>>> M::B::YAML instead).  It may be that at some time in the future it would 
>>> be useful to be able to /read/ YAML data (which requires the full YAML 
>>> distro) instead of just /writing/ YAML (which the compatibility layer 
>>> can handle nicely).
>> Any chance this could be generalized further to handle all the YAML that 
>> CPAN.pm needs and free us from the tyranny of YAML prerequisites?
>>
>> Module::MetaYAML?
> 
> The point of not just requiring the "real" YAML is to keep a low-level
> module-builder (Module::Build) from requiring other distributions.
> This doesn't apply to CPAN, and separating out a Module::MetaYAML
> would defeat this purpose for MB.

However, the latest Bundle::CPAN includes YAML, which uses 
Module::Install, requires 5.6.1 or better and build_requires Test::Base, 
which itself requires Spiffy.

So... when CPAN tells someone their CPAN is out of date and to upgrade 
with Bundle::CPAN or when someone wants to upgrade CPAN for some other 
reason -- for example, for better compatibility with Module::Build -- 
they're in for a world of hurt if any of the ballooning dependencies 
fail to build using the already installed CPAN/installer toolchain.

It doesn't really matter if M::B is self-contained or not if the other 
parts of the toolchain are fouled up.

David