tag:help.rubygems.org,2010-01-19:/discussions/suggestions/14696-handle-situation-properly-when-publishing-a-gem-whose-name-already-exists-on-rubygemsorgRubyGems.org: Discussion 2018-05-19T15:22:26Ztag:help.rubygems.org,2010-01-19:Comment/451990282018-05-04T17:09:41Z2018-05-04T17:09:41ZHandle situation properly when publishing a gem whose name already exists on Rubygems.org<div><p>Hi Jędrzej, thanks for writing in! I'm sorry that you found the gem name you wanted previously taken! We do have a policy, like most library repository systems, of globally unique library names. You can, of course, still create your library with your non-unique name, but will be unable to publish it through RubyGems.org. To allow multiple libraries with the same name would cause endless confusion for developers trying to maintain systems, manage updates, etc.</p>
<p>I'm sorry for the hassle you've encountered with this - I've run into it myself on occasion! Renaming your gem should be fairly straightforward; a quick Google search didn't turn up any automated tools for it, but plenty of articles on how to do it manually.</p></div>kerrizortag:help.rubygems.org,2010-01-19:Comment/451990282018-05-04T20:12:46Z2018-05-04T20:12:49ZHandle situation properly when publishing a gem whose name already exists on Rubygems.org<div><p>What's the solution to this problem? When you create a gem with a non-unique name you clearly change ownership of the gem to the owner of the gem that already exists on Rubygems.org and that is not cool at all. I would like to ask if you will change this.</p>
<p>Thanx<br>
Jędrek</p></div>JÄ™drzejtag:help.rubygems.org,2010-01-19:Comment/451990282018-05-19T15:22:23Z2018-05-19T15:22:23ZHandle situation properly when publishing a gem whose name already exists on Rubygems.org<div><p>Hi Jędrek,</p>
<p>The only ownership of a gem is only important in terms of the gem that is registered in the Rubygems.org system; if you want to have your own game of the same name, you are certainly welcome to, and can even allow others to use it by specifying a <code>git</code> location option in a Gemfile, or through manually downloading and installing. However, we have a "first in time" policy for the ownership of gem namespaces; if the gem in question is old, empty, etc, we encourage you to contact and work with the current owner to release the name to you (or add you as an owner so you can develop the tool in your own direction.)</p>
<p>// kerri</p></div>kerrizor