Re^3: Deprecating a CPAN Module

in reply to Re^2: Deprecating a CPAN Module
in thread Deprecating a CPAN Module

Please don't delete distributions from the CPAN … There are very valid reasons why someone might need to come back and fetch your last version released

Wouldn't BackPAN be sufficient for this purpose?

(Any time I upload to pause.cpan.org, a message is displayed encouraging me to clean up outdated distributions to help reduce the storage burden for CPAN and its mirrors. It assures me that users can always find old versions on BackPAN, as it intends to be a permanent archive that only under exceptional circumstances might a distribution be deleted from it.)

Comment on Re^3: Deprecating a CPAN Module

Replies are listed 'Best First'.
Re^4: Deprecating a CPAN Module by stevieb (Canon) on Jun 24, 2019 at 22:46 UTC
If it's on BackPAN, it won't be installed. You have to manually fetch it from there, and typically, most users wouldn't be familiar with the process when their 50-distribution project installation fails because something can't be found on the CPAN. Cleaning up your PAUSE versions just means removing the ones that aren't relatively current. If you remove the dist entirely from the CPAN (all versions essentially), it won't be found using typical CPAN tools period. ie. Standard CPAN tools don't go looking through BackPAN for previous versions. Those are considered legacy (at least this is my understanding).	[reply]
Re^5: Deprecating a CPAN Module by chrstphrchvz (Scribe) on Jun 25, 2019 at 00:17 UTC
That indeed is probably the case for standard (core) utilities; however cpanm will automatically fetch from BackPAN when needed, as long as `--dev` is not specified.	[reply]
Re^6: Deprecating a CPAN Module by stevieb (Canon) on Jun 25, 2019 at 01:43 UTC
I learned something new today :)	[reply]

In Section Seekers of Perl Wisdom