Ferret talk - Aug 2006 - Can'' t install.

Hi,

I want to install the Acts_as_ferret plugin so I tried "gem install 
ferret" and I get the following error:

C:\InstantRails\rails_apps\eatnewcastle>gem install ferret
Attempting local installation of ''ferret''
Local gem file not found: ferret*.gem
Attempting remote installation of ''ferret''
Building native extensions.  This could take a while...
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory - nmake



Any ideas?

-- 
Posted via http://www.ruby-forum.com/.

Hi Dave,

first of all: With gem install ferret you are installing ferret, the search
engine library of Dave Balmain. acts_as_ferret integrates this lib nicely
into rails applications. You install plugins by utilizing the ruby
script/plugin from withing your rails root. Check the acts_as_ferret trac
for details.

There are projects trac for ferret as well as for acts_as_ferret.
Doublecheck that you read the installation instructions on both of them.

The base for acts_as_ferret is ferret the library. Unfortunatly you are
trying to build the gem (for ferret the library) on windows. The latest and
greatest ferret (0.10.1) isn''t building without some heavy work that
seems
to be not suitable for a beginner. I''m myself didn''t further
try to build it
on windows. Dave Balmain will probably make a win32 gem of ferret in the
next few days that you won''t need to compile for yourself. The error
you are
reading complains about nmake not on your path which you would need for
building ferret. But you''d better wait for the win32 gem because nmake
alone
won''t help you anyways the bindings code isn''t yet optimized
for building on
windows.

So what should you do right now? You might install a gem of ferret below
version 0.10.0. The latest on this branch is 0.9.6 and then you might
install an acts_as_ferret plugin that is working with that branch of ferret.
For further details check out the acts_as_ferret trac.

That said even with the 0.9.6 gem you''ll be on the
''slow'' pure ruby version
of ferret while you are on windows. If you''ve got some time your best
option
might wait for the win32 gem of the ferret 0.10 branch.

Does this make sense to you? Don''t hesitate to ask!

Cheers,
Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/ferret-talk/attachments/20060828/3be711a8/attachment.html

Hi Jan,

Thanks for the detailed explanation. I myself tried to install ferret on 
windows. After going through a lot of hoops I gave up. I hit the dead 
end after a lot of work.

Anyway I spoke to my hosting provider about using ferret installed on 
their server and they allowed me to work with it. That was nice given 
that I would be doing sort of development work there.

I used aaf and everything works like a charm.

Since the only thing I did was to add a line stating
''acts_as_ferret'', I
believe the indexing is being done on the memory. In order to get the 
indexing on the hard drive I need to do something like

index = Index::Index.new(:path => ''/path/to/index'')

When I''m using aaf where do I specify this path. How do I tell aaf to 
keep all the indexed information at a particular path rather than 
keeping it in memory.

thanks.
Raj

-- 
Posted via http://www.ruby-forum.com/.

Hi!

On Tue, Aug 29, 2006 at 07:03:41AM +0200, Raj Singh
wrote:
> Hi Jan,
> 
> Thanks for the detailed explanation. I myself tried to install ferret on 
> windows. After going through a lot of hoops I gave up. I hit the dead 
> end after a lot of work.
seems to be easier to switch your working env to Linux or OS/X than
getting Ferret to build on Windows ;-)
> I used aaf and everything works like a charm.
> 
> Since the only thing I did was to add a line stating
''acts_as_ferret'', I
> believe the indexing is being done on the memory. In order to get the 
> indexing on the hard drive I need to do something like
> 
> index = Index::Index.new(:path => ''/path/to/index'')
> 
> When I''m using aaf where do I specify this path. How do I tell aaf
to
> keep all the indexed information at a particular path rather than 
> keeping it in memory.
aaf does store the index in the filesystem. The default path for doing
so is RAILS_ROOT/index/<environment>/class_name. So if your class is
named Article and you''re in development mode, the index will be stored
in RAILS_ROOT/index/development/article/.

If you like, you can specify another index directory with the index_dir
option:

class Article
  acts_as_ferret :index_dir => "#{RAILS_ROOT}/shared/index/article"
  [..]
end

Jens

-- 
webit! Gesellschaft f?r neue Medien mbH          www.webit.de
Dipl.-Wirtschaftsingenieur Jens Kr?mer       kraemer at webit.de
Schnorrstra?e 76                         Tel +49 351 46766  0
D-01069 Dresden                          Fax +49 351 46766 66