<drbrain>
mpapis: no, you would need reinstall. I think the Gemfile feature should be used for that purpose instead
<mpapis>
drbrain, I think this is showstopper for now for this feature, this is supposed to just work, any manual work for users is a step that will not be executed and will lead to problems
<drbrain>
mpapis: even with GEM_HOME_SHARED, it would have the same problem, I think
<drbrain>
I will still finish what I have so far
<mpapis>
hmm, then we need to solve this problem first - is they a way to specify !java platform?
<drbrain>
how do you mean?
<mpapis>
right now for the json gem there are two version with platform java, and without platform
<drbrain>
yes
<mpapis>
so if you install on jruby then the pltform will be picked, would it be possible to specify "not java" platform for the generic one?
<mpapis>
or maybe install all platforms without compiling extensions?
<mpapis>
+1 ^
<drbrain>
maybe ↑
<drbrain>
can you add a note to #596?
<mpapis>
sure
<drbrain>
I may not be able to fully solve this in time for 2.2
<drbrain>
but I approve of this idea
<drbrain>
right now I will shoot for bundler-like feature set, but with less disk space used
<drbrain>
a) user runs the equivalent of `bundle` in rubygems
<drbrain>
b) rubygems uses minimum disk space
<mpapis>
or maybe install gem in /platform subdir in case there are many versions of gem for different platforms
<mpapis>
even if that version is without platform restriction
<drbrain>
right now rubygems installs multiple platform versions alongside each other
<drbrain>
so that is difficult to change and maintain backwards compatibility
<mpapis>
I thought we can drop compatibility with this feature