On Jan 24, 2007, at 12:21 PM, Edward Summers wrote:
On Jan 24, 2007, at 12:11 PM, Erik Hatcher wrote:
Indeed, but it isn't the end of the world for them to add a --
source on there.
Absolutely not the end of the world--just not the ruby way :-)
Then why is there a --source switch? ;)
What I'd like to do is get Apache moved towards being Ruby savvy.
The ideal, to me, is getting deployments of releases to work cleanly
with "gem install" from the Apache infrastructure. No offense to
rubyforge at all (hi Rich and Tom!), I'm aiming idealistically at
making apache.org a 1st class Ruby software player.
I've been looking in the rubygems documentation today, as I presume
there is a way to register other gem servers besides rubyforge so
that "gem install solrb" would just work, and look in the appropriate
Apache place - perhaps analogous to the Maven repository?
I'll hit up Chad and Jim at Rails Edge in the next few days on this
topic and report back.
It'll be "solrb" though, not "solr" - it seems better to keep it a
separate name so it doesn't appear that you're actually installing
Solr too.
So people will:
require 'solrb'
and we need to:
svn mv lib/solr lib/solrb
svn mv lib/solr.rb lib/solrb.rb
?
It's a good question. My take was to call the .gem solrb, but the
library itself is solr, which is how it currently is set up. I'm not
quite sure though. I'm agile, and can be convinced to change it.
Erik
