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.
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.
This isn't about being unable to upgrade M::B in the middle of an
install without a second invocation - that hole is over here:
http://www.nntp.perl.org/group/perl.cpan.testers/2006/11/msg375686.html
No, I don't have any better ideas how to fix those... :(
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
