Excerpts from William Morgan's message of Wed Aug 19 13:02:26 -0700 2009: > I find it surprising too. I haven't seen taht behavior before. FWIW, Sup > does try and detect if bin/sup and lib/sup have mismatched versions, and > that didn't fire... I wonder if it's just sent.rb that's been loaded. > Did you somehow delete sent.rb from your git directory, or something > like that?
Nope. The git checkout is entirely intact, and it was quite a large number of modules getting misloaded. I ran an strace on the ruby process[*] and was able to plainly see that modules were being correctly loaded from ./lib until after /usr/lib/ruby/1.8/chronic.rb was loaded. After that, ruby would look for modules in /usr/lib/ruby/1.8 before ./lib. And sure enough, the first line of my chronic.rb has: $:.unshift File.dirname(__FILE__) # For use/testing when no gem is installed I'll go ahead and find the right place to file that bug, but at least the mystery is solved now. -Carl [*] http://cworth.org/~cworth/tmp/ruby-sup.strace
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
