@raggi @feyeleanor @headius what if RubyGems shipped with some gems preinstalled?
-
-
@bascule@feyeleanor@headius also, what happens when new bundler is loaded on old rubygems, then loads up Gem::DependencyInstaller? -
@bascule@feyeleanor@headius suddenly rubygems cannot activate it's required net/http version, because bundlers is activated -
@raggi@feyeleanor@headius what if the code was just vendored, and used the mechanism@drbrain described to activate a gem if available? -
@bascule@feyeleanor@headius@drbrain that mechanism has bugs i described yesterday also
End of conversation
New conversation -
-
-
@bascule@feyeleanor@headius so now it's rubygems that locks you to specific net/http versions not ruby, problem not solved -
@raggi@bascule@feyeleanor@headius what if putting everything in a stdlib gem similar to activesupport? not i like that, just throwing ids -
@godfat@raggi@bascule@feyeleanor Yeah...that is an interesting idea for me too. ruby-stdlib.gem -
@headius@raggi@bascule@feyeleanor So we would have much less conflicts, everything out of the box, yet a separate release cycle from MRI.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.