Reformatted excerpts from Carl Worth's message of 2009-08-19: > 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'd call that a bug in chronic. It shouldn't be screwing with the load path. Nice debug work. -- William <[email protected]> _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
