Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Issues with VERSION migration in a module suite

Received: by 10.204.141.4 with SMTP id k4mr2268387bku.6.1338380103278;
        Wed, 30 May 2012 05:15:03 -0700 (PDT)
Newsgroups: perl.cpan.testers.discuss
Path: e27ni16123bkw.0!nntp.google.com!news2.google.com!goblin3!goblin.stu.neva.ru!nntp.develooper.com!nntp.perl.org
Return-Path: <w.phillip.mo...@gmail.com>
Mailing-List: contact cpan-testers-discuss-h...@perl.org; run by ezmlm
Delivered-To: mailing list cpan-testers-disc...@perl.org
Received: (qmail 7034 invoked from network); 30 May 2012 12:04:43 -0000
Received: from x1.develooper.com (207.171.7.70)
  by x6.develooper.com with SMTP; 30 May 2012 12:04:43 -0000
Received: (qmail 29577 invoked by uid 225); 30 May 2012 12:04:42 -0000
Delivered-To: cpan-testers-disc...@perl.org
Received: (qmail 29573 invoked by alias); 30 May 2012 12:04:42 -0000
X-Spam-Status: No, hits=-2.7 required=8.0
	tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: la.mx.develooper.com
Received: from mail-gh0-f173.google.com (HELO mail-gh0-f173.google.com) (209.85.160.173)
    by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Wed, 30 May 2012 05:04:39 -0700
Received: by ghrr14 with SMTP id r14so3402771ghr.18
        for <cpan-testers-disc...@perl.org>; Wed, 30 May 2012 05:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=YDHWjOjPMeTFH90DyoLvLCR/t/jjhr3mzQDejwycSJQ=;
        b=Q+31RdiFsP5c+BGhjtNhBFFHbx6PmiDZW/QQIzPPmESCIY06xIDTu2cd2BM8N0Ccjm
         L6BZzbUl2ps+8TNu4jjCilBMPpyvmEhGXd0gPcwn8eYsUK01vuLPedVm9VWrr45BhaEf
         kHzOmdvvXvfElPYkmltgb9EtVey4WR5fqTEEcXovodxHm10mjOm/YgxG/f7mSRxcq2h0
         J0bI4MBdFJzxhQMe7p57hIvUDNu5LlazbMVCDw/0WWIhKpMIvx3B8sQDdWlV2hyu+Fkw
         8hgpM+8On8Heh7JnXjgoHroMWOwEDxIPyDF6ebgSgzdeDWhhFvaofduXd2S/Oi0Yw5DU
         nzOw==
MIME-Version: 1.0
Received: by 10.50.208.8 with SMTP id ma8mr10320396igc.41.1338379475200; Wed,
 30 May 2012 05:04:35 -0700 (PDT)
Received: by 10.231.188.72 with HTTP; Wed, 30 May 2012 05:04:35 -0700 (PDT)
Date: Wed, 30 May 2012 08:04:35 -0400
Message-ID: <CAJY0+QAQhBgcKdet8xKXdrQt2O5sd5RFkHoD3TU2Csd-Ns7...@mail.gmail.com>
Subject: Issues with VERSION migration in a module suite
To: cpan-testers-disc...@perl.org
Approved: n...@nntp.perl.org
From: w.phillip.mo...@gmail.com (Phillip Moore)
Content-Type: text/plain; charset=ISO-8859-1

I just took over one of my older module suites (NetApp.pm, which is
actually about 20 distinct NetApp::* classes), and decided to change
the versioning scheme to match the style I'm using in all the rest of
my code.   In the older release, which was written back in 2008, I
used a per-file SVN Revision tag as the VERSION, which led to
per-module versions in the 100s.   The version of the distribution was
1.1.2, and I had been using v-strings for versions back in those days.

In all my newer code, I dropped the individual module versions, and I
use a single VERSION for the entire distro.  I updated the distro
version to 2.002, but PAUSE did NOT like this file when I uploaded it,
because all of the individual module versions appeared to decrease,
not increase.  Now, the 02packages.txt.gz data shows the problem:

NetApp                            2.002  W/WP/WPMOORE/NetApp-2.002.tar.gz
NetApp::Aggregate              332.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Aggregate::Plex        203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Aggregate::RAIDGroup   203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Filer                  410.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Filer::Export          203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Filer::License         203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Filer::Option          203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Filer::TimeoutCache    334.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Filer::Version         203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Qtree                  334.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Snapmirror             275.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Snapmirror::Destination 203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Snapmirror::Source     203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Snapshot               275.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Snapshot::Delta        203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Snapshot::Schedule     203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Volume                 419.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz
NetApp::Volume::Source         203.000000  W/WP/WPMOORE/NetApp-1.1.2.tgz

There's an obvious solution here: make the distro version something
with a major version greater then 419, and then all of these will
increase, PAUSE will be happy, and I can keep moving forward.

However, is this the only solution?  Is there any way to convince
PAUSE that those older module versions didn't matter?

I suspect not, but before I jump from 1.1.2 to 2.002 and then 500.0001
(420.0001 is *very*, very tempting.... :-) I'd like to be sure there's
no other choice.