Re: Trimming the CPAN - "Automatic Purging"

> On 27 Mar 2010, at 00:59, Andy Armstrong wrote:

> > On 27 Mar 2010, at 00:59, Elaine Ashton wrote:
> > The only snag I can forsee in trimming back on the abundance of modules is 
the case where some modules have version requirements for other modules where 
it will barf with a mismatch/newer version of the required module (I bumped 
into this recently but can't remember exactly which module it was) but I think 
it's rare and the practise should be discouraged.
> 
> 
> Maybe that could be solved by having the clients (and maybe search.cpan.org) 
automagically fall back to a backpan mirror?
> 
> And, yes, if it's considered a good idea I am prepared to do something about 
it.

Exactly what I wrote in my previous mail, nobody commented I was wondering if 
I was wrong!

In any case. We do now have a better understanding of the problem and most 
important we have a "real" user (Elaine) wishing for something to be done.

Andreas, Chris, Tatsuhiko and other have done a tremendous job implementing 
stuff but I must admit that I would have like to see a list of what they are 
implementing. Not to mention the need to see a context diagram. IMVHO the 
first thing we should do is have a requirement list of what CPAN actors 
(clients, pause, mirrors, search engines, ...) should do. Maybe that document 
already exists somewhere. 

What implication we may have on CPAN, ExtUtils, Module::Build, and all other , 
still unknown, modules are, I believe, not to be under estimated.

Andy (since you are the first to really volunteer (and now you don't have any 
choice anymore;)), count me in whatever development time is needed to get 
things moving. 

Ask, this thread is getting a tad long and although I'm very happy to see more 
input, requirements and ideas, Would it be possible to see a some condensed 
results somewhere?

Cheers, Nadim.