From: Tom Copeland <tom@...>
Date: 2007-02-04T08:59:28+09:00
Subject: Re: Gem Namespaces

On Sun, 2007-02-04 at 02:43 +0900, Trans wrote:
> I know I will probably be lambasted by the usual lambasting sort,
> nonetheless I think its worth suggesting that all gems have a project
> namespace. As things stand a project on Rubyforge can create gems with
> any name at all --which can readily conflict with gems in another
> project. A few projects in particular suck up lots of name real-
> estate, in just 3 projects alone one can find 59 gems, some with names
> as simple as "traits".

A note on this - anyone on RubyForge can create and release a gem called
anything they want.  I could create a Rails 4.2 gem and release it on my
"foo" project.  It just won't get deployed to the RubyForge gem index.
But people can still come to my "foo" project and download the gem via
the regular file download pages and then install it.  

Another option is to set up a gem index on your project's virtual host -
foo.rubyforge.org - and folks can install with gem --source.

Those options may alleviate the namespacing problem somewhat; food for
thought, anyhow.

Yours,

tom