in reply to Changing a module's namespace on CPAN

Recently I have been contemplating changing the namespace for one of my modules
Why?
How is it best to handle a namespace change?
By not changing the namespace (picking a good one to begin with) :)
Should I release an updated module version whose sole purpose is to install the renamed module in the new namespace on CPAN?
Technically, that's the only way to "rename" a module, by releasing a new module with a different name. But if thats all you're going to do, you really shouldn't. But, if you insist on doing it, make sure you release a final version under the old name, making it clear to its users that the name has changed, and what kind of support they can expect...

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

  • Comment on Re: Changing a module's namespace on CPAN

Replies are listed 'Best First'.
Re^2: Changing a module's namespace on CPAN
by jacques (Priest) on Jun 22, 2005 at 04:43 UTC
    Why?

    Sometimes things change, and modules evolve beyond their original intention. I don't think it happens often, but I know that the potential for it to happen exists.