Re: Subclass? Plugin? Mixin? Monkey Patch?

On Jun 18, 2008, at 11:07, Eric Wilhelm wrote:

>  http://www.nntp.perl.org/group/perl.module.build/2008/03/msg1298.html
>
> There are more if you point your favorite search engine at
> nntp.perl.org/group/perl.module.build and ask about plugins.

Thanks, I'll take a look.

>> How hard can it be? (He asks, ignoring the dragons.)
>
> The dragons I've seen are the difficulty of testing and lack of
> coverage - particularly with regard to multiple environments and
> configurations.

Eh. You do what you can. I added filters to SVN::Notify, and testing  
was a bit tricky, but not bad.

>> Huh? Plugins can be distributed separately, with their own
>> dependencies, I'm sure.
>
> If a plugin is not needed for the 'build', 'test', or 'install'  
> targets
> on a target (user) machine, there should be a way to make it optional.

That can come later. We should do things incrementally -- or else  
they'd never get done at all.

> We also have to make sure that whatever gets printed to the
> compatibility Makefile.PL accounts for that or uses a plain M::B - or
> just refuse to write a Makefile.PL if it's not easily solvable.

Right. That shouldn't be hard, either.

Best,

David