3 ms·
This is dealt with in the FAQ - but the short answer is that Gemcutter mirrors all gems from RubyForge. If you want to push directly to Gemcutter instead of let
by rufo 17y ago
This is dealt with in the FAQ - but the short answer is that Gemcutter mirrors all gems from RubyForge. If you want to push directly to Gemcutter instead of letting Gemcutter mirror it, you need to go through a migration process to verify you are the owner.
So no, you can't just upload a gem titled "rails" to Gemcutter and have it override the Rails team's gems.
- btucker 17y agoBut is that also true for previously github-hosted gems? Can I push a gem called 'why-hpricot' for example?
- rufo 17y agoIs there any reason you can't post a gem called why-hpricot to RubyForge and have it override GitHub? This doesn't seem like a new problem to me. If this concerns you, just edit the sources list of your .gemrc file manually and make sure RubyForge is at the top and Gemutter is at the bottom.
- btucker 17y agoThat's a very valid point since for most people gems.github.com comes after RubyForge in the source list. Oy... makes me think running 'gem install' without --source is just a bad idea.
- pjhyett 17y agoWe added code at least a year ago to prevent people from building gems with the name of a gem already hosted on rubyforge. That being said, the rubygem library itself really needs some type of namespacing solution to solve the problem once and for all instead of requiring gem hosts to implement hacks like we did. Fortunately, I've heard rumblings that they may be working on something.