I know that some of the module creation tools include a requirement for the particular perl version. For example, the boilerplate from h2xs includes by default, a dependency on the current perl version that it is being run on. In many cases, this is not applicable.
In my case, I'm stuck with a 5.6.1 perl at work, but keep finding modules that refuse to load. Sometimes this is genuine with use of 5.8 syntax or semantics. However, there are other times when hacking the module to comment out the dependency allows the module to pass all tests and install.
An example that has occurred today is theDamian's IO::Prompt. I've commented out the use 5.008 and it passes tests.
I know 5.6.1 is quite old now, but it's a pain having modules with artificial dependencies to 5.008, when there's no reason.
--
Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)
In reply to Artificial perl version dependencies by rinceWind
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |