# from Adam Kennedy
# on Sunday 29 October 2006 03:56 am:
>> 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).
What is "inc support"? Whatever it is, I doubt that we need it here.
>So now you have bundled the plugin Module::Install-style
No. I haven't. We're not bundling anything here except the wee 20-line
"chooser snippet" from my previous mail. MyCustomBuilder.pm is the
subclass for and by the author of Foo.pm.
MyCustomBuilder will be a subclass of either Module::Build or
Module::Build::Pluggable -- depending on which is available.
And,
not:
"which one is
available at Build.PL time",
rather:
"which one is
available at ./Build time"
.
Can we please work with a more concrete example? As I understand it,
you're saying that Foo.pm may need Module::Build->check_prereq() to do
something special depending on the platform? So, you want to use a
plugin which provides check_prereq?
If so, then Module::Build::Plugin::CheckPrereq would be a static
build_requires, as would Module::Build::Pluggable.
--Eric
--
I arise in the morning torn between a desire to improve the world and a
desire to enjoy the world. This makes it hard to plan the day.
--E.B. White
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
