On 1/2/07, Jon Jensen <[EMAIL PROTECTED]> wrote:
On Tue, 2 Jan 2007, David Fetter wrote:
>>> I seem to recall CPAN has a limit of how many versions they let you
>>> keep around. Two seems far too low. But in any case, if we can't
>>> increase the number on CPAN, is there somewhere else we can keep them?
>>> I can provide public space if it's needed.
>>
>> Much better would be to put them on pgfoundry.
>
> Better still would be to expire them.
What do you mean by "expire"? We can say they're unsupported but still
preserve an archive of them as a service. Why go to great lengths to put
them in the memory hole?
Some relevant points about CPAN here:
1) CPAN doesn't have any intrinsic limit on the number of versions of
a module that I know of. Some of the older modules on CPAN have tons
of ancient revisions still out there.
2) Many older versions of DBD::Pg are on CPAN, they're just not in the
same author directory (someone else already pointed this out in this
thread, and where to see them at)
3) Modules which are deleted from the main CPAN for whatever reason
(outdated by newer bugfix releases in the same major version series,
too old to support, etc) always live on in the BackPAN for legacy
users that really need them. You can find all the old releases of
DBD::Pg that have been deleted to date at:
http://backpan.cpan.org/modules/by-module/DBD
Given all of these things, I think it sounds perfectly fine to release
a new version which only supports 7.4+, and it also sounds fine to
clear out some of the ancient versions currently on CPAN.
-- Brandon
