dev-lang/perl: Make new OLDVERSEN strategy for NEXTVER
authorKent Fredric <kentnl@gentoo.org>
Sun, 21 May 2017 00:07:32 +0000 (12:07 +1200)
committerKent Fredric <kentnl@gentoo.org>
Sun, 21 May 2017 15:04:54 +0000 (03:04 +1200)
commit38a9278233b784c5115e344b9b3d8263d5268f2e
tree583a8d3c58338325640b06162d7a9c7fac4dc231
parente27e066be274861b127297b6a749975e3d355d80
dev-lang/perl: Make new OLDVERSEN strategy for NEXTVER

As per discussion on #gentoo-perl, this is slated as a strategy for
5.26, as it means people who upgrade to 5.26 retain existing installed
modules in their @INC

This serves as additional defence against portage build-order issues,
which are going to become especially pertinent given we're going to
have a substantial number of packages likely to fail configure or test.

So its important that people who can't rebuild packages can still have
existing versions continue to work on the newer perl where possible.

Package-Manager: Portage-2.3.5, Repoman-2.3.2
dev-lang/perl/perl-5.26.9999.ebuild