On Sun, Aug 9, 2009 at 4:02 PM, Eric Wilhelm<enoba...@gmail.com> wrote: > For a less-fiddly automatic setting of configure_requires, we might want > to have a table of named features mapped to version numbers. But I > would still use alpha numbers in that table - just warn the user during > ACTION_dist() if their required feature is in alpha (implied by being a > bigger number than the last major release extracted from the current > $VERSION.) Maybe some pod with '=item' entries under each =head2 > $VERSION section could be cooked into a .pm at build time.
I thought about this, but I worry about maintenance/upkeep. I think X.YY is simple and will DTRT for > 95% of users. David
