Re: namespace clash : how do I rename my module safely

Is there any cleanup work that should be done on CPAN / PAUSE as well? Would a PAUSE 'Delete Files' be appropriate at this point? I don't know (why I am asking the question).

--MidLifeXis

Comment on Re: namespace clash : how do I rename my module safely

Replies are listed 'Best First'.
Re^2: namespace clash : how do I rename my module safely by gideondsouza (Pilgrim) on Jan 31, 2013 at 16:17 UTC
Yes :) I did know I have to delete bad versions and I deleted v0.01 of my Dancer plugin, but is it practise to only keep the latest version on CPAN? I will then delete all my old dists	[reply]
Re^3: namespace clash : how do I rename my module safely by MidLifeXis (Monsignor) on Jan 31, 2013 at 16:25 UTC
I don't know that deleting old versions is necessary, especially if a backward-breaking incompatibility has been added. :-) --MidLifeXis	[reply]
Re^3: namespace clash : how do I rename my module safely by tmharish (Friar) on Feb 02, 2013 at 08:11 UTC
I read a note somewhere on PAUSE about how "CPAN is getting large, please delete old versions - they will be on backpan" ( Cant seem to find it anywhere now ). I have also noticed that Google sometimes shows the older module above the later version - so its possible that a visitor from Google ends up on an older version of the module. I generally remove all old modules ( other than the previous one ) - The exception of course is when I stop providing backward compatibility. There seem to be other reasons for removing older versions which I don't really subscribe to.	[reply]