On Wed, May 30, 2012 at 6:46 AM, David Golden <[email protected]> wrote:
> On Wed, May 30, 2012 at 8:04 AM, Phillip Moore
> <[email protected]> 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 modules/distributions from CPAN, waiting until
> it clears out of the 02packages file, and then re-uploading with all
> 2.003 VERSION strings. That might work, or might not, but I don't
> think you lose anything other than time by trying it.
Does PAUSE ever forget about a file entirely? This implies not:
http://pause.perl.org/pause/query?ACTION=pause_04about#upload
For security reasons you will never be able to upload a file with
identical name again.
> Note that people with older versions installed might have trouble
> upgrading without a forced installation of a particular distribution.
> The most user-friendly thing to do is to bump up to NNN.0001 or
> whatever.
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 that the best way to handle things to derive a single version number
which is at least `max(@versions) + $n` and use that for all modules. It
might look a little weird, but oh well -- it's justified from an engineering
standpoint. At least unifying the version numbers produces a sane outcome,
albeit at the expense of violating DRY.
Marvin Humphrey
