$VERSION in Opcode

[Nicholas Clark <nick@ccl4.org>]

How do we cope with $VERSION in Opcode.pm (and Safe.pm) where 5.8.x and 5.10.x
have diverged? Kitten life expectancy goes down whenever CPAN has two modules
that differ claim the same $VERSION, yet we also don't want an arms race of
"newest version of Opcode.pm is in perl-5.8.9.tar.bz2, won't upgrade your
5.10.0 unless you issue force install"

(See appended message)

Nicholas Clark

On Thu, Sep 11, 2008 at 05:38:18PM +0100, Steve Hay wrote:
> Nicholas Clark wrote:
> > On Thu, Sep 11, 2008 at 01:15:06PM +0100, Steve Hay wrote:
> >> I thought I'd have a look at item 3 in
> >> 
> >>
> http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2008-09/msg00074.
> >> html 
> >> 
> >> Sure enough, there are lots of modules in maint-5.8 that differ from
> >> 5.8.8 but have the same VERSION. Many of these are non-dual-lived
> >> modules, and mostly seem to be due to changes having been applied to
> >> blead with no VERSION change, and then getting merged into maint-5.8.
> >> 
> >> What's the best thing to do in these cases? Is it simply to bump the
> >> VERSION of the affected files in blead and then leave you to merge
> >> those changes into maint-5.8?
> > 
> > Yes, that would be exactly what I'd do. For all the non-dual lived
> > modules, commit to blead, then merge across.
> 
> I started looking at this and got stuck quickly.
> 
> Opcode.pm in maint-5.8 is VERSION 1.06, the same as in perl-5.8.8, but
> the file is different so the VERSION needs bumping.
> 
> The question is: what should it be bumped to? The obvious answer of 1.07
> arguably doesn't make sense because 5.10.0 has already escaped
> containing an Opcode.pm VERSION 1.11! Actually, in this particular case
> it might make sense to make it an intermediate number because
> maint-5.8's version contains more than 5.8.8 but less than what ended up
> in 5.10.0. However, such a plan wouldn't work in general because if
> 5.10.0's version happened to have been 1.07 then there wouldn't be an
> intermediate number to use.
> 
> On the other hand, making it 1.12 doesn't make sense either, given that
> there is less in this version than what's in the version that has
> already been released as 1.11.
> 
> Feel free to ping this question onto p5p if more input is needed.

---

Follow-Ups from:

"Rafael Garcia-Suarez" <rgarciasuarez@gmail.com>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---