Eric Wilhelm wrote:
# from Adam Kennedy
# on Saturday 28 October 2006 06:11 pm:
If you need the plugin installed at perl Build.PL-time, then anything
that would not work under dynamic_config: 0 breaks the plugin.
inc/MyCustomBuilder.pm
package MyCustomBuilder;
use inc::builder;
use base builder('Module::Build::Pluggable');
Build.PL
use inc::MyCustomBuilder;
# blah blah blah
I don't need anything at Build.PL-time there. What am I missing?
Last time I checked, Module::Build doesn't have inc support, and can't
dump the files there for you (you'd have to do it by hand).
Secondly, it doesn't fit the Module::Build installation model, which is
that the end user has to install the build modules.
So now you have bundled the plugin Module::Install-style, so the user
gets the plugin from when the module was released (even if there's a
newer one available) but the version of Module::Build itself continues
to be upgraded.
If the plugin API changes incompatibly with your plugin, your module
goes boom, and we have to trust that you will reliably upgrade your
module to fix it (something that we are discovering from the
Module::Install experience people don't generally do).
Adam K
