According the rubyforge docs, if you try to release a gem of the same name as a gem already released in a different project, it will just ignore you (e g not add it to the gem index). So we won't break anything, but probably won't have any effect. According to Jim Weirich of the rubygems team, (who conveniently enough happens to be sitting next to me as I type this), platform name is not counted as part of the gem name so we would definitely have to have our gem released as part of the ruby-debug project for it to be seen. So if we want to go this route we should start talking to the ruby-debug guys.
Also of interest, in the beta release of rubygems, it will take your platform into account automatically. What this means is that if someone does "gem install ruby-debug-base" from jruby they will get the java platform version withouth having to choose it (provide we've released it so they can see it of course). Did anyone have any thoughts on my long rambling post on whether and what to prepackage into JRuby? On Oct 31, 2007 11:49 AM, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > 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 > >
