Ken Williams wrote: > On Jul 17, 2006, at 4:53 PM, Eric Wilhelm wrote: > > If you want to maintain parallel EU::MM and M::B files for version.pm, > > that's up to you. I'm just wondering what happens when any of these > > (there may be more -- this is just a quick check against 5.8.8 core) > > decide to switch to using M::B? > > > > Module::Signature > > ExtUtils::ParseXS > > Archive::Tar > > Pod::Readme > > ExtUtils::CBuilder > > YAML > > Pod::HTML > > I guess the most streamlined solution would be for those modules to > bundle M::B rather than the other way around, because they only > build_require it, whereas we really require them at runtime.
So whenever M::B decides to create a _new_ dependency, that dependency will have to bundle M::B? That doesn't sound right. And look at it from another angle: Having to bundle something that you need only at build time is a greater "waste" then having to bundle some- thing that you regularly need at run time. And yet another angle: If YAML (for instance) has to bundle M::B, it then will have to bundle Module::Signature, ExtUtils::ParseXS, Archive::Tar, etc., too, or the bundled M::B won't be able to run in order to install YAML and you won't have solved anything. Summing it up, that approach seems to me like a very, very bad idea. Recursive build dependencies is a broken concept by design.
pgpHRegdjZCBq.pgp
Description: PGP signature
