Andreas J. Koenig wrote:
>>>>>> On Tue, 11 Sep 2007 02:21:12 -0700, Michael G Schwern <[EMAIL
>>>>>> PROTECTED]> said:
>
> > This already exists, it is the "passthrough" option to
> Module::Build::Compat.
>
> > small
> > A small Makefile.PL will be created that passes all
> > functionality through to the Build.PL script in the same
> > directory. The user must already have Module::Build
> installed
> > in order to use this, or else they’ll get a
> module‐not‐found
> > error.
>
> > passthrough
> > This is just like the "small" option above, but if
> > Module::Build is not already installed on the user’s
> system,
> > the script will offer to use "CPAN.pm" to download it and
> > install it before continuing with the build.
>
> Both options do not look like what I suggested. I'll repeat in
> shortspeak, my posting was apparently too long.
>
> diplomatic writes Makefile.PL (diplomatic) and Makefile-trad.PL
> (traditional). On the user box: The diplomatic calls the
> traditional if no Module::Build is install, otherwise it plays the
> Build.PL. In the latter case a small Makefile is provided too, so
> that a call to 'make' translates to a a call to './Build'.
>
> I hope this is short enough to make spot and focus match.
I think what you want is something that combines "traditional" and "small".
The Makefile.PL would look something like this...
if( have Module::Build ) {
translate the Makefile.PL arguments to Build.PL arguments
exec Build.PL
}
...normal MakeMaker stuff...
Ok. There's all the problems of the author having to maintain duplicate
installers and the MakeMaker / Module::Build translation problems. That
leaves me asking "why?" It seems the point is to avoid installing
Module::Build. Why would one want to avoid that as opposed to any other
prerequisite? What problem does this solve?
It smells an awful lot like when people were griping about having to install
Test::More and we made gyrations so they didn't have to.
--
Whip me, beat me, make my code compatible with VMS!
