Issues with VERSION migration in a module suite

2012-05-30 Thread Phillip Moore
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

Re: Issues with VERSION migration in a module suite

2012-05-30 Thread Dean Hamstead
Hopefully version 420 will be stable? Dean On Wed, 30 May 2012 08:04:35 -0400, Phillip Moore wrote: 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

Re: Issues with VERSION migration in a module suite

2012-05-30 Thread David Golden
On Wed, May 30, 2012 at 8:04 AM, Phillip Moore w.phillip.mo...@gmail.com wrote: However, is this the only solution?  Is there any way to convince PAUSE that those older module versions didn't matter? No. I'm pretty sure versions have to increase. However, you could try *deleting* all the

Re: Issues with VERSION migration in a module suite

2012-05-30 Thread Marvin Humphrey
On Wed, May 30, 2012 at 6:46 AM, David Golden xda...@gmail.com wrote: On Wed, May 30, 2012 at 8:04 AM, Phillip Moore w.phillip.mo...@gmail.com wrote: However, is this the only solution?  Is there any way to convince PAUSE that those older module versions didn't matter? No.  I'm pretty sure

Re: CPAN Testers Daily Summary Report

2012-05-30 Thread David Golden
I see the deps properly specified in a distribution built from a github clone, but that doesn't seem to be the same as what's on CPAN. -- David On Tue, May 29, 2012 at 5:45 AM, Dean Hamstead d...@fragfest.com.au wrote: Im hoping some charitable soul can help me out here. For some reason i

Re: Issues with VERSION migration in a module suite

2012-05-30 Thread Marvin Humphrey
On Wed, May 30, 2012 at 7:40 AM, David Golden xda...@gmail.com wrote: I really wish that versions and dependencies were expressed at the distro level rather than the module/package level.  Allowing multiple version numbers within an atomic unit of installation doesn't make sense. I agree.  

Re: Fwd: Failed: PAUSE indexer report WPMOORE/NetApp-500.001.tar.gz

2012-05-30 Thread Dean Hamstead
Can dist::zilla do it for you automatically? D On Wed, 30 May 2012 15:02:02 -0400, Phillip Moore wrote: I attempted to upload NetApp-500.001 to workaround the high version numbers in the individual modules, but PAUSE is very unhappy with the individual $VERSION definitions going away. Isn't

Re: CPAN Testers Daily Summary Report

2012-05-30 Thread Dean Hamstead
yes my bad, i have pushed changes to git (using cvs 9-5, i forget to push) previously i listed out SVN::Ra SVN::Client SVN::Core and got this result http://www.cpantesters.org/cpan/report/a81acbac-a73f-11e1-9d6f-f6dbfa7543f5 I then looked on cpan to see what was going on with these three

Re: Fwd: Failed: PAUSE indexer report WPMOORE/NetApp-500.001.tar.gz

2012-05-30 Thread Serguei Trouchelle
Dean Hamstead wrote: Can dist::zilla do it for you automatically? Yes, Dist::Zilla::Plugin::PkgVersion (and/or Dist::Zilla::Plugin::AutoVersion for very lazy authors). -- S.T.