On Aug 21, 2009, at 17:17 , Jim Weirich wrote:
On Aug 21, 2009, at 7:29 PM, Ryan Davis wrote:
Apparently I was wrong and the behavior is intended. I think it is
wrong (but in this case I also think this is a case of bad code as
well). I think that gem plugin activation should be explicit.
Really? What is the intended purpose?
Eric should weigh in on this as it is his design... It had something
to do with install hooks and the like being runnable from someone
else's script, not just `gem install`. But I'm paraphrasing heavily.
I think that's a good goal, but I would rather see plugin loading be
made explicit. If you're writing a script to interact with rubygems
(the system), it is already on you to use it correctly so you might as
well be the one to load the plugins. If you're just using rubygems
(aka require), it shouldn't have to load plugins.
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
