From: Ryan Davis Date: 2010-02-05T16:36:34+09:00 Subject: Re: rdoc_osx_dictionary 1.2.0 Released On Feb 4, 2010, at 21:25 , Phrogz wrote: > On Feb 3, 1:27 pm, Benoit Daloze wrote: >> On 3 February 2010 20:32, Ryan Davis wrote: >>> rdoc_osx_dictionary version 1.2.0 has been released! > > 1) Why do I never see Ryan's original announcements on the > comp.lang.ruby side of things, but only others' responses? See: > http://groups.google.com/group/comp.lang.ruby/browse_frm/thread/1fe6802b6db67ee5/4fbe195e7fca9340#4fbe195e7fca9340 I have absolutely no idea. Blame google? No... my guess is that it is prolly the gateway... but really I don't know. I never read it that way. Why do you? Are there tangible benefits? >>> * > > 2) Ryan, you do wonderful work, but why oh why must you continue to > hostenormous piles of wholly disparate projects under a single web > site? because it drives our stats up? :D > The home page for 'this' project, http://seattlerb.rubyforge.org/, > doesn't even list rdoc_osx_dictionary. That's because I'm lazy and haven't automated that page yet :) >>> rdoc via Apple's Dictionary.app. Automatically builds and installs an >>> Apple Dictionary with all rdoc nicely formatted. > > Sadly, no glory for me. I'm wholly guessing that this is a gem I > install (given no instructions in the quoted email, and I'm assuming > not in the original). Given that, here's what I get: > > phrogz$ sudo gem install rdoc_osx_dictionary > Password: > Successfully installed rdoc_osx_dictionary-1.2.0 > 1 gem installed > Installing ri documentation for rdoc_osx_dictionary-1.2.0... > Installing RDoc documentation for rdoc_osx_dictionary-1.2.0... > updating OSX ruby + gem dictionary, if necessary > /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in > `gem_original_require': no such file to load -- rdoc_osx_dictionary > (LoadError) > from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in > `require' > from /usr/local/lib/ruby/gems/1.9.1/gems/rdoc_osx_dictionary-1.0.1/ > bin/rdoc_osx_dictionary:6 I just had a bug reported about the gem using PATH to figure out what ruby to invoke... possibly this is related? does `which gem` and `which ruby` resolve to the same install for you? I'd guess not based on the mix of /usr/local/lib and /Library/Ruby in your backtrace. > I love the idea of this project; anything I can do to help debug > further, please let me know.