Re: best practices for module renaming

2011-02-08 Thread David Cantrell
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

2011-02-08 Thread David Nicol
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.