From: Trans <transfire@...>
Date: 2007-02-04T04:02:50+09:00
Subject: Re: Gem Namespaces



On Feb 3, 12:49 pm, "Austin Ziegler" <halosta...@gmail.com> wrote:

> RubyForge currently ensures that the only traits gem that will exist
> on RubyForge is the one from codeforpeople -- because they were the
> first to release such. It's not quite a namespace, but it prevents the
> conflict you were talking about.

That's too bad, I think. For instance, I have my own rendition of
rubyforge.rb that I made based on the Ara's original. This script used
to be tucked away in the Reap project, but I'm reorgainizing my tools
and I was thinking of releasing this separately. But what wll I call
it since "rubyforge" is already used? Are other's going to be happy if
I call it "rubyforge2" ?

> There are, I think, worse problems than possible gem name collisions
> (require-able contents collisions are more likely, IMO).

Luckily if two projects have similar names it probably b/c they serve
nearly the same purpose and you'd use only one or the other. But your
right, that' can be a problem too.

T.