Re: Re: Re: Re: Re: The quantity vs. quality lesson

Modules should never be removed. Other scripts and applications may depend on them, and I consider backward compatibility to be an important feature.

Rather write a comment on cpanratings if you think that a module is bad, or add a bug report on rt.cpan.org. Share your knowledge with the community, it is already possible. Right now.

Comment on Re: Re: Re: Re: Re: The quantity vs. quality lesson

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Re: The quantity vs. quality lesson by BlaisePascal (Monk) on Jun 02, 2004 at 19:14 UTC
Is it really the case that scripts and applications that depend on old modules will get broken if they are removed from CPAN? I know when I use modules on CPAN I make local copies, and don't run them from the 'net. I'm not sure it's feasible to do otherwise.	[reply]
Re^7: The quantity vs. quality lesson by eserte (Deacon) on Jun 03, 2004 at 09:27 UTC
Well, there's backpan, which holds everything ever uploaded to CPAN. But if a module is not anymore at CPAN, then it is more difficult to find it through search.cpan.org or impossible to install with CPAN.pm.	[reply]
Re^7: The quantity vs. quality lesson by adrianh (Chancellor) on Jun 06, 2004 at 08:47 UTC
Is it really the case that scripts and applications that depend on old modules will get broken if they are removed from CPAN? They would be broken in the sense that if module Foo depending on CPAN module Bar, and module Bar was removed, then Foo could no longer be easily installed via CPAN. The person who wanted to use Foo would have to figure out what had happened and install Bar manually from backpan.	[reply]


Do you know where your variables are?
	PerlMonks