Yitzchak Scott-Thoennes wrote:
> On Fri, Feb 17, 2006 at 02:01:30PM +0000, Nicholas Clark wrote:
>> The thread on what YAML version Module::Build needs, and how to upgrade
>> correctly if there isn't >=0.50 suggests that solving these "Module::Build
>> needs upgrading" issues isn't yet battle tested.
>
> I missed that thread. What was the subject?
Here the thread (it started on the YAML list):
http://tinyurl.com/barey
(I can't figure out how to get Mailman to show the thread properly).
> Module::Build doesn't
> need YAML at all (though authors really should have it to generate a
> fleshed-out META.yml). And the current development version should
> work fine with current versions of YAML.
It's a little more complicated than that. M::B 0.2611 cannot be installed with
YAML support unless YAML is >= 0.35 and < 0.49 (it's an autofeature). However
if you reinstall YAML 0.58 after you install M::B, then everything still works.
If M::B 0.28 required YAML 0.58 for the YAML feature to be auto-enabled, and
the author had not already upgraded YAML, then the YAML feature would be
disabled without much in the way of warning. It still wouldn't affect the users
(who don't need YAML at all).
However, this has just given me an idea: Bundle::Module::Build::Authors. This
would install all of the "recommends" modules as well as the latest YAML.
In any case, I've recommended that the version.pm support be pulled out of
consideration for 0.28, due to these complications.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
