Re: best practices for module renaming
On Mon, Feb 07, 2011 at 08:59:40PM +0100, Xavier Noria wrote: Hi, I am the author of Net::FluidDB, which let's you talk to FluidDB. FluidDB has been renamed to Fluidinfo, and I should rename the module in accordance. Is there a recommended way to do this? Or should I just upload a different distribution and document the rename? I'd upload a new distribution, rename the module, and also include a backward-compatibility wrapper module. -- David Cantrell | Reality Engineer, Ministry of Information
Re: best practices for module renaming
On Tue, Feb 8, 2011 at 6:29 AM, David Cantrell da...@cantrell.org.uk wrote: On Mon, Feb 07, 2011 at 08:59:40PM +0100, Xavier Noria wrote: Hi, I am the author of Net::FluidDB, which let's you talk to FluidDB. FluidDB has been renamed to Fluidinfo, and I should rename the module in accordance. Is there a recommended way to do this? Or should I just upload a different distribution and document the rename? I'd upload a new distribution, rename the module, and also include a backward-compatibility wrapper module. I would do nothing until there is a change in Fluidinfo that makes the FluidDB module stop working. I would also continue to use the old name inappropriately to annoy the marketeers. And if the change really is name-only, I might upload a very light Fluidinfo module that simply aliases the name space -- probably using direct symbol table manipulation, instead of using the Alias module.
best practices for module renaming
Hi, I am the author of Net::FluidDB, which let's you talk to FluidDB. FluidDB has been renamed to Fluidinfo, and I should rename the module in accordance. Is there a recommended way to do this? Or should I just upload a different distribution and document the rename?
Re: best practices for module renaming
On Mon, 7 Feb 2011, Xavier Noria wrote: Hi, I am the author of Net::FluidDB, which let's you talk to FluidDB. FluidDB has been renamed to Fluidinfo, and I should rename the module in accordance. Is there a recommended way to do this? Or should I just upload a different distribution and document the rename? Yes to your last question. You could also upload one last version of Net::FluidDB and update its docs to point to the new name. -dave /* http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) */
Re: best practices for module renaming
On Mon, Feb 7, 2011 at 12:48 PM, Dave Rolsky auta...@urth.org wrote: On Mon, 7 Feb 2011, Xavier Noria wrote: Hi, I am the author of Net::FluidDB, which let's you talk to FluidDB. FluidDB has been renamed to Fluidinfo, and I should rename the module in accordance. Is there a recommended way to do this? Or should I just upload a different distribution and document the rename? Yes to your last question. You could also upload one last version of Net::FluidDB and update its docs to point to the new name. You probably also want to keep Net::FluidDB around as a wrapper module so that you don't break backward compatibility. # # ##