It would be so much more convenient if the auto tools like cpanp and cpanm would take module versions into consideration and didn't jump from 1.x to 2.0 for example, instead following the current 1.x branch until the user makes a conscientious decision to upgrade.
Well, hah :)
See https://metacpan.org/pod/CPAN::Meta::Spec#prereqs for the bare-bone-ness
See Task for advanced bones
All you need, to get cpan/cpanm not to jump from 1.x to 2.x is add checks in all the related Makefile.PL equivalents, that does die "ABORTING; WILL NOT FORCE UPGRADE TO 2X VERSION WITHOUT Task::Foo2X\n" if not require Task::Foo2x;
Then Task::Foo2x does explicitly install DWALIN/Foo-2.0.1.tar.gz and all the stuff
Then you get everything you want, but naturally you have to update the 1.x version to have this enhanced Makefile.PL equivalents
In reply to Re^3: Controlled CPAN breakage
by Anonymous Monk
in thread Controlled CPAN distribution breakage
by dwalin
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |