I don't use it, but contrary to what James just said, if I did deleting it would affect me.
We rebuild our environment very night, including downloading all cpan modules anew (automatically getting the latest one if it has been updated). So, if anyone else has a similar environment and does a similar autofetch, then they would be impacted (although in such cases, they would probably already have converted to the renamed new module). John Macdonald Software Engineer Ontario Institute for Cancer Research MaRS Centre 661 University Avenue Suite 510 Toronto, Ontario Canada M5G 0A3 Tel: Email: john.macdon...@oicr.on.ca Toll-free: 1-866-678-6427 Twitter: @OICR_news www.oicr.on.ca This message and any attachments may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this message in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this message may not be that of the organization. ________________________________________ From: James E Keenan [jk...@verizon.net] Sent: June 8, 2015 12:59 PM To: module-authors@perl.org Subject: Re: good form for discontinuing a module On 06/07/2015 02:38 PM, Chris Marshall wrote: > The PDL::FFTW module is out-of-date and has been essentially broken > for a long time without anyone being aware of it. It has been marked > deprecated in favor of PDL::FFTW3 and I think now is the time to finally > remove it from CPAN. > > Should I just go ahead an delete it or is there another, intermediate > way to "more softly" transition in case someone, somewhere is actually > using/requiring PDL::FFTW? > If someone is actually using PDL::FFTW, then they already have it -- right? So their current use has no dependency on whether or not the module still is indexed on CPAN. So, depending on how long a deprecation period you or the maintainers announced, I don't see a barrier to deletion. Thank you very much. Jim Keenan
