Re: [Module::Build] Re: [Yaml-core] yaml_dump on version objects

[John P. <jpe...@ro...>]

Ken Williams wrote:
> 
> On Feb 16, 2006, at 11:46 AM, John Peacock wrote:
> 
>> Is there some overriding reason you are avoiding upgrading the YAML 
>> prereq to 0.50 (which in itself isn't even the current rev)?
> 
> Good question.  I guess not, though this is the first time I think we'd 
> upgrade an auto-feature dependency, and it has just occurred to me that 
> it'll catch people by surprise if they currently have that feature 
> enabled.  It will suddenly get non-enabled without much warning.

Can't the 0.28 installer test for the auto-feature already being enabled 
*and* whether YAML is new enough and then upgrade that to a mandatory 
prereq?  It would mean that the auto_feature would still quote 0.35, but 
then before running create_build_script, you have to ask if they want to 
upgrade YAML *or* disable YAML support.  Alternatively, check the 
existing auto-feature setting before calling ModuleBuildBuilder and DTRT...

This may be something to consider for future development: conditional 
autofeatures that take a coderef for additional processing.  In pseudocode:

    auto_features => {
                      YAML_support =>
                      {
                       description => "Can write fully-functional 
META.yml files",
                       requires => { YAML => check_yaml() },
                      },

where check_yaml() returns either true (if the existing version is 
already acceptable) or can prompt the user and insert a new requires() 
stanza if the user accepts the additional dependency, *or* it returns 
false and that auto-feature is disable.

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