in reply to (OT) cpan love gone wrong

Seriously, I don't see what the issue is - CGI::PathInfo was released in 2005, and you seem to have released a module of the same name (resp. LEOCHARRE::CGI::PathInfo) in 2007. Namespaces on CPAN are handed out on a first-come first-served base, so the 2005 release has first rights on that name.

If you want to use the name CGI::PathInfo in your modules, there is nobody holding you back, but you'll forego the installation via CPAN and the CPAN testers, obviously. Also, I consider it unwise and rude to release a distribution with the same name as somebody else's, whether or not the two do very different things.

I don't see blindly registering any namespace as useful - if you don't have the code to back it up, the namespace should be left free for the taking. A bad example is Javascript::Engine, which just exists as a download placeholder for the (IMO badly named) JE. A counterexample to this is Alien which at least has a manifesto describing the idea. But the package name you mention even has code backing it, so I'm missing your point.

Update: Weird - upon looking again, I must have hallucinated LEOCHARRE::CGI::PathInfo, as there is no such package now...

Replies are listed 'Best First'.
Re^2: (OT) cpan love gone wrong
by leocharre (Priest) on Feb 12, 2008 at 15:53 UTC

    Something is ridiculously strange here- and I am quite confused. This was my module CGI::PathInfo

    I would never release a module of the name that was already present on cpan. Even if the module's namespace was not officially registered via cpan.

    I may have made a terrible screqup- maybe when I sought for CGI::PathInfo before- it didn't show up- and maybe the other module recently got the namespace approved.. ??? My version has been up for a while, this is the first I hear of a conflict.

    I have to look further into this. I will rename my module regardless.