On Mon, May 21, 2007 at 02:56:18PM -0400, John Peacock wrote:
> I received a complaint against my SVN::Notify::Build distro:
>
> https://rt.cpan.org/Public/Bug/Display.html?id=27183
>
> that has me annoyed. I provide a compatibility Makefile.PL so that
> users without Module::Build installed will get bootstrapped into the
> modern era. For whatever reason, this wouldn't work with the OP's
> system and caused his smokes to just burn CPU. That's not my problem.
>
What is the point of the compatibility file if it requires
Module::Build to work correctly?
If you want to support older installations not capable of using
Module::Build, it should work without it, and the failure is a valid
problem.
If you only care about supporting the minimum perl version supported
by the oldest version of M::B compatible with your module, then just delete
it. The bootstrap path is to install M::B.
> My problem is that the OP seems to think I should provide a fully EU::MM
> compatible Makefile.PL, because installing M::B is too much of a
> hardship. I can see that the OP has entered another bug:
>
> https://rt.cpan.org/Public/Bug/Display.html?id=27208
>
I read the post as implying that the OP doesn't care if M::B install
is forced or not. The problem is the incompatible Makefile.PL.
I would just delete it and let the older systems users figure out
how to bootstrap with M::B. It may or may not be useful to support the use of
older M::B versions.
Austin
