One bummer about taking Module::Build out of core

https://github.com/Perl-Toolchain-Gang/Module-Build/issues/22

The upshot is that lots of modules will no longer be able to use M::B if
they want to, through no fault of their own, because M::B uses them.
 Currently they could use M::B, even though it seems like a circular
dependency, because they know it's already present in the core, so the M::B
dependency is satisfied if a certain minimum perl version is available.

Maybe this is an unavoidable consequence of using Perl tools to build Perl
tools, I'm not sure.

`configure_requires` doesn't help much here.  But an autobundling feature
(putting the installer tool, whether M::B or EU::MM or whatever, in an inc/
directory) seems like it could do the trick.

 -Ken

• One bummer about taking Module::Build out of core by Ken Williams
• Re: One bummer about taking Module::Build out of core by Ricardo Signes
• Re: One bummer about taking Module::Build out of core by David Golden
• Re: One bummer about taking Module::Build out of core by Ken Williams
• Re: One bummer about taking Module::Build out of core by David Golden
• Re: One bummer about taking Module::Build out of core by Ken Williams
• Re: One bummer about taking Module::Build out of core by Leon Timmermans
• Re: One bummer about taking Module::Build out of core by David Golden