You see, CPANPLUS falls into the same category as M::B for me, namely "solutions looking for a problem".
CPANPLUS falls into the same category as M::B for me too - except it's the category of "thank goodness - at last a solution to some long standing problems" :-)
I wish them well, but you'll have to forgive my not seeing a compelling reason to switch.
Then don't ;-) I was just pointing out another solution for automatically handling M::B's Build.PL files. I believe a patch has gone into CPAN too, so hopefully that will make it into 5.10 and make the whole issue moot.
Indeed, if you avoid the 0.22 and 0.23 releases CPAN should cope quite happily with a M::B install now, as long as there is a passthrough Makefile.PL.
As a fellow member of the module-authoring elite, I've never needed to extend EU::MM. I'm not sure whose experience is more representative here.
Of course, if you don't need the functionality then don't use it. I'm not trying to force people to move to M::B - honest :-)
I just that, for me, the improvements that M::B gives me in building and installing modules are worth the minor-to-non-existant pain of dealing with CPANPLUS and/or passthrough Makefile.PL files that I have encountered.
I take this as a challenge... people manage to write major programs in Prolog and Haskell, despite their declarative natures ;). YMMV, of course.
I'm not knocking declarative languages. I've done a lot of Prolog in my time (I even reinvent it in Perl on occasion :-). It's just that inserting bits of Perl into a makefile via EU::MM is non-trivial.
In reply to Re^5: Module::Starter, a helper for new module authors
by adrianh
in thread Module::Starter, a helper for new module authors
by petdance
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |