On Feb 17, 2006, at 8:01 AM, Nicholas Clark wrote:
It won't hurt them, but it will cause immense pain for anyone
wanting to
ship a module that uses a Build.PL - those developers will be
forced to
decide whether to cut out anyone with an old Module::Build, or code
their
Build.PL to use that version and work around the deficiencies.
Those authors should just be able to put a 'build_requires'
dependency on the right version of Module::Build.
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.
That's a different issue - the problem there is how to handle
increases in 'feature' requirements, e.g. the 'yaml_support' feature
for M::B.
-Ken
