Just released Ferret 0.11.1. Hopefully this will fix most of the
problems people were having. Now that I know gcc hides stack overflows
on Ubuntu because -fstack-protector is set, I won’t get caught by that
one again. Anyone know any other gotchas I should be aware of on
Ubuntu.
Please try the new version and let me know if you are still having
problems with it. I have until the end of the week to work on Ferret
as much as I need to so I’d like to deal with as many issues as
possible within that time.
Just released Ferret 0.11.1. Hopefully this will fix most of the
problems people were having. Now that I know gcc hides stack overflows
on Ubuntu because -fstack-protector is set, I won’t get caught by that
one again. Anyone know any other gotchas I should be aware of on
Ubuntu.
Please try the new version and let me know if you are still having
problems with it. I have until the end of the week to work on Ferret
as much as I need to so I’d like to deal with as many issues as
possible within that time.
Cheers,
Dave
Dave,
I’m getting the following error on my Mac OS/Locomotive environment when
starting mongrel:
/Applications/Locomotive2/Bundles/rmagickRailsSept2006_x86.locobundle/framework/lib/ruby/gems/1.8/gems/ferret-0.11.1/lib/ferret/document.rb:45:
Document is not a class (TypeError)
from
/Applications/Locomotive2/Bundles/rmagickRailsSept2006_x86.locobundle/framework/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in require' from /Applications/Locomotive2/Bundles/rmagickRailsSept2006_x86.locobundle/framework/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:inrequire’
from
/Applications/Locomotive2/Bundles/rmagickRailsSept2006_x86.locobundle/framework/lib/ruby/gems/1.8/gems/ferret-0.11.1/lib/ferret.rb:27
from
/Applications/Locomotive2/Bundles/rmagickRailsSept2006_x86.locobundle/framework/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:33:in require' from /Applications/Locomotive2/Bundles/rmagickRailsSept2006_x86.locobundle/framework/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:inrequire’
Is this something with my configuration or a bug with the new version?
mongrel starts cleanly with 0.11.0…
Just released Ferret 0.11.1. Hopefully this will fix most of the
problems people were having. Now that I know gcc hides stack overflows
on Ubuntu because -fstack-protector is set, I won’t get caught by that
one again. Anyone know any other gotchas I should be aware of on
Ubuntu.
at least macos does not know, how to handle that parameter…
Just released Ferret 0.11.1. Hopefully this will fix most of the
problems people were having. Now that I know gcc hides stack overflows
on Ubuntu because -fstack-protector is set, I won’t get caught by that
one again. Anyone know any other gotchas I should be aware of on
Ubuntu.
Great stuff Dave.
My fairly standard Debian box fails on gem install too.
make clean
Successfully installed ferret-0.11.1
Installing ri documentation for ferret-0.11.1…
Installing RDoc documentation for ferret-0.11.1…
then I get this when I try and run my rails app:
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in gem_original_require': no such file to load -- ferret_ext (LoadError) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:inrequire’
from
/usr/local/lib/ruby/gems/1.8/gems/ferret-0.11.1/lib/ferret.rb:25
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:33:in gem_original_require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:33:inrequire’
-Mike
David B. wrote:
Hey guys,
Just released Ferret 0.11.1. Hopefully this will fix most of the
problems people were having. Now that I know gcc hides stack overflows
on Ubuntu because -fstack-protector is set, I won’t get caught by that
one again. Anyone know any other gotchas I should be aware of on
Ubuntu.
Please try the new version and let me know if you are still having
problems with it. I have until the end of the week to work on Ferret
as much as I need to so I’d like to deal with as many issues as
possible within that time.
Gem files will remain installed in
/usr/lib/ruby/gems/1.8/gems/ferret-0.11.1 for inspection.
Results logged to
/usr/lib/ruby/gems/1.8/gems/ferret-0.11.1/ext/gem_make.out
on Centos 4.4 (and by extension RHEL 4) with ruby 1.8.4. FYI.
Thanks guys, looks like I’ll be putting another version out very soon.
I’m just trying to set up a rake task to do a quick release to
rubyforge. I’m looking at xforge[1] at the moment. Anyone have any
alternative recommendations?
Awesome.
The gem installs fine.
The index rebuilds fine and passes all my search tests (including that
nasty A Team BA Barrachus thang)
Great stuff Dave.
Thanks guys, looks like I’ll be putting another version out very soon.
I’m just trying to set up a rake task to do a quick release to
rubyforge. I’m looking at xforge[1] at the moment. Anyone have any
alternative recommendations?
On Wed, Feb 28, 2007 at 12:23:15PM +1100, David B. wrote:
Thanks guys, looks like I’ll be putting another version out very soon.
I’m just trying to set up a rake task to do a quick release to
rubyforge. I’m looking at xforge[1] at the moment. Anyone have any
alternative recommendations?
I recently set up something like that in acts_as_ferret. I use the
rubyforge gem which is called from some rake tasks.
Excerpts from Patrick R.'s message of Wed Feb 28 05:52:57 -0800
2007:
Have you looked at Hoe? It includes a Rake task to Package and upload
to Rubyforge.
I use Hoe for several projects and it’s great. The Rakefile for Sup (a
complex package with 6 dependencies) is only 47 lines and has tasks for
building the gem, uploading it RubyForge and posting announcments.
The only issues I have are a) it expects a very specific directory
setup, and if you are fitting it on a pre-existing project you either
have to conform or you have to be very careful (e.g. it expects doc/ to
contain only generated rdoc pages, and so deletes that directory with no
warning for several tasks); and b) it adds itself as a dependency to the
gem, for no good reason, and you have to monkey-patch it to stop that.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.