require hacks not affecting -r command-line option?

[Francis Hwang]

So, I'm trying to override Kernel.require, doing a similar thing to it
that Rubygems does when you use -rubygems. But one thing I notice is
that it doesn't seem possible to have the change to Kernel.require
affect subsequent uses of the -r command-line option. So if you're
trying to use log4r as a gem, say, then

ruby -rubygems -rlog4r -e "puts 'blah blah blah'"

won't work. -rubygems will affect require, but not in any way that
-rlog4r can get to.

Can somebody explain to me how this is working (or not working), and if
there's any way around this? If there isn't a way around this, maybe I
should be submitting an RCR?

f.

 

[ts]

F> Can somebody explain to me how this is working (or not working),

With -r ruby call directly rb_require()



Guy Decoux