It has occurred to me that a lot of people need some of the fixes I
make to Ferret ASAP and don’t like having to wait to long for the gem.
On the other hand, it is a bit of a pain to download and install from
subversion because then you need to uninstall when the next gem comes
out. So I thought I may as well put some instructions out as to how
you can build your own Ferret gem that will get overridden by the next
official version to come out. Here goes:
$ svn co svn://www.davebalmain.com/exp/ ferret
$ cd ferret/ruby/
Now optionally run the tests to make sure I haven’t checked any dodgy
changes in:
$ rake
build the gem. REL should be the current release and then append 0.1.
If you do this a second time between release append 0.2 and so on. The
current version is 0.10.5 so we’ll build 0.10.5.1:
0.10.9. I will continue compiling against that version until another
version of Ruby marked “stable” comes out. I have no idea why this
problem is occuring. Unfortunately I can’t reproduce the problem here
which makes it even more difficult for me to solve. Actually, if
anyone has built the gem themselves, please send it to me. I’d like to
try a build from a different system.
We’re having some troubles with ferret on Win32, the illegal
character issue that has been discussed here before. Am I correct
that the heart of the issue is that the version of ruby we are using
is different from the one used to compile the win32 gem of ferret?
If so, what version of ruby is the latest gem compiled for? What was
the last win32 gem to be compiled with Ruby 1.8.4-20?
build the gem. REL should be the current release and then append 0.1.
If you do this a second time between release append 0.2 and so on. The
current version is 0.10.5 so we’ll build 0.10.5.1:
$ rake package REL=0.10.5.1
How do we know what the version is when we download using:
svn co svn://www.davebalmain.com/exp ferret
Do we look at ruby/lib/ferret_version.rb each time?
That’s why you build a gem. You can use gem uninstall. It isn’t
really necessary to delete previous versions though when using a gems
will take care of using the latest version. If you’ve installed using
setup.rb you’ll need to delete the files by hand. You should be able
to find our where it is installed using the ‘gemwhich’ command.
Which creates a gem package, simply removing that gem package puts you
back
at the previous version you had…it’s pretty self-contained.
For example, I compiled a version of 0.10.9.1, but removed it for API
change
reasons, so I simply removed my 0.10.9.1 folder (but still kept my
0.10.9
folder (under the ruby/1.8/gems folder), and everything was back in
sync.
Hope this helps.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.