Martin Krauskopf wrote:
I'm not sure how the rubyforge behaves in such a case when two gems with
the same name are offered by the two projects. Probably just offers list
of them. In such a case it would be ok since gem tool will offer
something like:
1. ruby-debug-base 0.9.3 (ruby)
2. ruby-debug-base 0.9.3 (mswin32)
3. ruby-debug-base 0.9.3 (java)
I think. And since now it's up to the user. So I would say yes, let's
go. We always can delete the released file in case of some problems. And
probably most of the users do not share gem repository anyway as others
said.
I'm not certain it works this way. Sync up with the ruby-debug
maintainer and see if we can just get it released as part of their
normal process, and otherwise *confirm first* that us releasing a
ruby-debug gem of the same general name will not break the existing
released versions.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
