Re: CPAN / new Perl 5 features / Perl upgrade conundrum
[email protected] (Joaquin Ferrero) Thu, 31 May 2012 16:52:49 +0200
| Newsgroups | perl.perl5.porters,perl.documentation |
|---|---|
| Message-ID | <[email protected]> |
El 31/05/12 16:27, Christian Walde escribió: > On Thu, 31 May 2012 12:34:39 +0200, David Cantrell <[email protected]> wrote: > >> On Wed, May 30, 2012 at 11:00:46AM -0400, Michael Peters wrote: >> >>> Sure, just release a new 1.x version of your module that works for older >>> perls and then a new 2.x version of your module for newer perls and >>> cpXXXan will pick up which ones works for which versions of perl and >>> gives the right one to the right user. >> >> Provided that the PAUSE lets you do that - I don't know if it allows >> version numbers to go backwards. But yes, assuming that it does, then >> that is exactly what would happen. > > Actually, it does not. The pause indexer will reject your upload if it detects version numbers going backwards. > > On the other hand: Releasing a 2.x.y that works on 5.6, then a 2.x.y+1 that works on 5.8, then a 2.x.y+2 that works on 5.16 should do the job fine and the cpanxxx mirrors should pick up the newer versions working on older perls. > This is a problem for POD2::ES, also, because we want to publish POD2::ES v5.14.2.09 and POD2::ES v5.16.0.01 at the same time, mainly for to save the translated OOP pods into v5.14 branch (perlboot, perlbot, perltooc and perltoot are deleted at Perl v5.16) -- JF PerlSpanish Team