discuss: dev-lang/perl should block perl-core modules older than the bundled ones
I'm not always sure that's the case. For instance, even via CPAN toolchain, its not uncommon to downgrade to an older version than shipped with perl for the purposes of testing. As not all core things have minimum requirements forced upon them by other core things. And occasionally, it may be useful to do that in ::gentoo, for example, in a case where a newer version of something in perl breaks tests and thus you need an older version of that thing ( eg: there was a case with POD Syntax having this problem ) to get tests to pass ( though in that specific example, I'd simply say patch out the stupid test, but not all problems work that way ). That is to say, if we don't want users using older versions of things, they should be removed from tree entirely. Not stipulating they need newer versions even when none of the software involved declares it needs newer versions of things.
(In reply to Kent Fredric from comment #1) > I'm not always sure that's the case. > > For instance, even via CPAN toolchain, its not uncommon to downgrade to an > older version than shipped with perl for the purposes of testing. > > As not all core things have minimum requirements forced upon them by other > core things. > > And occasionally, it may be useful to do that in ::gentoo, for example, in a > case where a newer version of something in perl breaks tests and thus you > need an older version of that thing ( eg: there was a case with POD Syntax > having this problem ) to get tests to pass ( though in that specific > example, I'd simply say patch out the stupid test, but not all problems work > that way ). > > That is to say, if we don't want users using older versions of things, they > should be removed from tree entirely. Not stipulating they need newer > versions even when none of the software involved declares it needs newer > versions of things. OK let's forget it.
