Chris Nelson wrote:
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?
I'm somewhat on the fence about preinstalling. Many people may never
want the debugging stuff, but it seems like a good thing to include.
Pre-installing would also let us get 1.0.2 out today with ruby-debug
support built-in while we figure out the release questions. What's the
total size of the gems once installed?
And a question for Martin: would packing ruby-debug and friends into
JRuby make it easier to get into NB 6 final?
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
