Let's start to use year as version, eg:
bash$ perl -Mv5.2018
Perl v5.2018.0 required--this is only v5.6.2, stopped.
BEGIN failed--compilation aborted.
- signal users that perl5 is still alive and up-to-date :-)
- (just guessing) customers / managers may easier understand why they should approve upgrade
Switch from 3+3 to 4+3 (eg: 5.2018001). Numerical comparison will still work though some pretty prints may by broken.
Even v5.6.2 reports required version properly
bash$ perl -Mv5.2018
Perl v5.2018.0 required--this is only v5.6.2, stopped.
BEGIN failed--compilation aborted.
Usage without vstring will need tuning
bash$ perl -M5.2018
Perl v5.201.800 required--this is only v5.6.2, stopped.
use VERSION should enforce vstring, for example it should be syntax error if number higher than last version before this change will be adopted is used
bash$ perl Makefile.PL
Warning: Perl version 5.026 or higher required. We run 5.016003.
bash$ perl Makefile.PL
Warning: Perl version 5.2018 or higher required. We run 5.016003.
bash$ perl Build.PL
Checking prerequisites...
requires:
! perl (5.16.3) is installed, but we need version >= 5.26
bash$ perl Build.PL
Checking prerequisites...
requires:
! perl (5.16.3) is installed, but we need version >= 5.2018