On Jun 6, 12:20 pm, Evan Phoenix <e...@fallingsnow.net> wrote: > No, there are gems that specify multiple values for this for extensions and > embedded libraries. There is no reason to lose configurability of this.
Sure. I do so myself in one of my gems. But even if RubyGems would never change this because of backward compatibility, I'm asking a more philosophical question: could it work? I curious about cases were having multiple require paths has proven essential --where it just wouldn't be possible, or at least way too painful, without it. _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
