Deprecating CPAN modules?

dgaramond2 has asked for the wisdom of the Perl Monks concerning the following question:

Is there a mechanism or convention on deprecating my own CPAN module? For example I see that some other author has done an equivalent and better module, and I want to encourage people to use that module instead. Preferably without deleting my module out of existence or even releasing a new version just to say "this module is deprecated".

Comment on Deprecating CPAN modules?

Replies are listed 'Best First'.
Re: Deprecating CPAN modules? by DrHyde (Prior) on Apr 13, 2007 at 11:39 UTC
You'll need to upload a new version, if only to add some text to the docs to say that it's deprecated. I would also make the module spit out warnings when used (which the user could turn off) and then remove it from the CPAN after a year or so. It would also be neighbourly to notify any other CPAN authors who have dependencies on your module - you can hunt them down through this page.	[reply]
Re: Deprecating CPAN modules? by explorer (Chaplain) on Apr 13, 2007 at 10:05 UTC
Exists various methods for deprecated I see that authors mark modules with (DEPRECATED) front the description line.	[reply]
Re^2: Deprecating CPAN modules? by xdg (Monsignor) on Apr 13, 2007 at 10:43 UTC
Actually, it needs to be noted in the `NAME` section of the pod to show up in CPAN search. `=head1 NAME Foo::Bar - (Deprecated) Use Bam::Baz instead` [download] -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply] [d/l] [select]


There's more than one way to do things
	PerlMonks