On Mon, May 21, 2007 at 04:13:53PM -0400, John Peacock wrote:
> Austin Schutz wrote:
> > What is the point of the compatibility file if it requires
> >Module::Build to work correctly?
>
> But the compatibility file *itself* doesn't require Module::Build - it
> merely checks to see whether it M::B is installed and installs it if it
> isn't, then proceeds to test/install the containing module using the
> just-installed M::B.
>
So... the compatibility mode gains nothing but creates problems.
These days, who is the target audience for these files? Is anyone left
who doesn't know - and shouldn't find out - what to do with a Build.PL file?
What is the conceptual target system where compatibility mode is (still)
useful?
I'm picturing some older system which has an older CPAN.pm and doesn't
know what to do with a Build.PL file. In this case you could upgrade to
a CPAN(PLUS)?.pm which is compatible. It seems reasonable IMO to expect users
to upgrade to newer tools if they want to use newer modules. Maybe I'm missing
something obvious here. Wouldn't be the first time. :-)
Austin
