On 15/02/03 21:43 -0600, Ken Williams wrote:
>
> On Thursday, February 13, 2003, at 03:30 AM, [EMAIL PROTECTED] wrote:
> > Tonite at Portland.pm I gave a lightning talk entitled "MakeMaker Is
> > DOOMED!
> > or MakeMaker Is Dead! Long Live Module::Build!".
>
> Excellent. =) I should bring a Grim Reaper mask to YAPC/TPC this year.
I went to the talk. It got me to thinking about CPAN::MakeMaker and its
relationship to Module::Build.
Given:
The goal of CP::MM is to allow authors to write very simple/clean
Makefile.PLs that can potentially "turn on" very powerful features
like "bundling" with the flick of a switch.
The Makefile.PL produces a Makefile.
Then:
There is no reason why CP::MM can't produce a Makefile that wraps
Module::Build!
If the author has a version of Module::Build on there system that
is sufficient to handle the options that the author has requested
of CPAN::MakeMaker, then CP::MM will (optionally??) bundle M::B
into the author's dist. After that nobody is the wiser. Everything
just works.
Except that if the USER is installing on a makeless system, CP::MM
will prompt them to use Build instead.
Conclusions:
CP::MM becomes a migration tool for moving over to Module::Build.
The users always have the correct version of M::B, because it is
bundled in. (Just like CP::MM itself)
CP::MM focuses on "refactoring fancy functionality into simple
switches".
M::B focuses on replacing MakeMaker.
Yay! Thoughts?
Cheers, Brian
