develooper Front page | | Postings from April 2007

Re: Adding configure_requires to META.yml

Thread Previous | Thread Next
Eric Wilhelm
April 17, 2007 22:51
Re: Adding configure_requires to META.yml
Message ID:
# from Adam Kennedy
# on Sunday 18 March 2007 04:28 am:

>> Also - what happens if a user has an old CPAN, an old M::B, and
>> downloads a META.yml containing a configure_requires entry?
>>  Presumably that entry would be ignored and the user would miss the
>> dependency altogether.

>There is no graceful way to deal with this.
>As for putting something in the Build.PL... yes, I guess, but it would 
>be big, ugly, and stuck at the top of the Build.PL scripts for several 

What about:
  use Module::Build 0.29;

It's not particularly graceful, but I would hope it would be obvious 
enough what needed to be done.  When computer says:

  Module::Build version y.yy required--this is only version x.xx

even call-center-grade troubleshooting guides instruct the user to 
install version y.yy.  Maybe it's not always that easy?

Anyway, it's "I told you once" if configure_requires is in the META.yml, 
so detonation seems warranted.  Once one passes the "bridge out" sign, 
things get more complicated.

As for dragging older's out of the stone age, I suppose we could 
try to detect what CPAN*.pm version was installing M::B and very, very 
loudly recommend an upgrade?

"Everything goes wrong all at once."
--Quantized Revision of Murphy's Law

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About