fri: how to use correct gem index

[s.ross]

I installed fri and it is somehow thinking it should look for doc on
old gems. For example, I have actionpack-2.0.2 installed, yet fri is
looking for actionpack-1.13.3.

I did a gem cleanup and then a rake redoc

Typing:

fri -L form_for

gives me:

/opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_index.rb:346:in `initialize': No such file or directory - /opt/
local/lib/ruby/gems/1.8/doc/actionpack-1.13.3/ri/ActionView/Helpers/
FormHelper/form_for-i.yaml (Errno::ENOENT)
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_index.rb:346:in `open'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_index.rb:346:in `get_method'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_service.rb:219:in `info'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_service.rb:422:in `capture_stdout'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_service.rb:218:in `info'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/bin/fri:342
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/bin/fri:337:in
`each'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/bin/fri:337
from /opt/local/bin/fri:16:in `load'
from /opt/local/bin/fri:16

Should bugs be reported on rubyforge? (not sure if this is a bug or
user error.)

Thx

 

[Stefano Crocco]

Alle Tuesday 19 February 2008, s.ross ha scritto:

I installed fri and it is somehow thinking it should look for doc on
old gems. For example, I have actionpack-2.0.2 installed, yet fri is
looking for actionpack-1.13.3.

I did a gem cleanup and then a rake redoc

Typing:

fri -L form_for

gives me:

/opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_index.rb:346:in `initialize': No such file or directory - /opt/
local/lib/ruby/gems/1.8/doc/actionpack-1.13.3/ri/ActionView/Helpers/
FormHelper/form_for-i.yaml (Errno::ENOENT)
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_index.rb:346:in `open'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_index.rb:346:in `get_method'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_service.rb:219:in `info'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_service.rb:422:in `capture_stdout'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/lib/fastri/
ri_service.rb:218:in `info'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/bin/fri:342
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/bin/fri:337:in
`each'
from /opt/local/lib/ruby/gems/1.8/gems/fastri-0.3.1.1/bin/fri:337
from /opt/local/bin/fri:16:in `load'
from /opt/local/bin/fri:16

Should bugs be reported on rubyforge? (not sure if this is a bug or
user error.)

Thx

Have you tried rebuilding the fastri index?

fastri-server -b

or, if you want to use full-text search,

fastri-server -Bb

Stefano

 

[s.ross]

Alle Tuesday 19 February 2008, s.ross ha scritto:

Have you tried rebuilding the fastri index?

fastri-server -b

or, if you want to use full-text search,

fastri-server -Bb

Stefano

Worked like a charm. Is there any writeup on the Web about this? All I
found was the rubyforge page and the home page at http://eigenclass.org/hiki.rb?fastri
is serving up a 503.

Thx,

--s