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.
I'm thinking M::B should bundle even its optional dependencies so
it can
ask me if I want the feature and dwiw without me having to install
stuff
and then reconfigure it (I'm still not clear on exactly how the
optional features are configured.)
Agreed. The various optional dependencies have more dependencies
themselves, though, so it can get to be a pretty big web. The
required dependencies are generally pretty lean.
-Ken
