tag:help.rubygems.org,2010-01-19:/discussions/questions/124-how-to-change-platform-of-existing-gemRubyGems.org: Discussion 2012-04-16T23:20:22Ztag:help.rubygems.org,2010-01-19:Comment/153057742012-04-16T17:08:14Z2012-04-16T17:08:14ZHow to change platform of existing gem<div><p>I suggest you yank those older versions. We don't support the
ability to change the platform of a gem.</p></div>Evan Phoenixtag:help.rubygems.org,2010-01-19:Comment/153057742012-04-16T17:09:50Z2012-04-16T17:09:50ZHow to change platform of existing gem<div><p>Short answer: you can't</p>
<p>Long answer: gems were automatically downloaded by mirrors and
also downloaded by users. You can't push gems over existing ones
because downloaded won't equal cached and you can evict cached gems
for end-user systems.</p>
<p>Once a gem has been pushed, was pushed.</p>
<p>If you want to avoid a gem from being installed, you can yank
it.</p></div>Luis Lavenatag:help.rubygems.org,2010-01-19:Comment/153057742012-04-16T18:29:44Z2012-04-16T18:29:44ZHow to change platform of existing gem<div><p>I get it, and hopefully this work-around committed in the
bundler gem<br>
codebase will fix our problems too:</p>
<p><a href=
"https://github.com/carlhuda/bundler/commit/8ef7b59427321cec7409408d02b7ea4fd0beb9a4">
https://github.com/carlhuda/bundler/commit/8ef7b59427321cec7409408d...</a></p>
<p>...I suppose it's just a PITA that we were allowed to push gems
with invalid .gemspec's in the first place!</p>
<p>Thanks for your efforts!</p></div>David Colebatchtag:help.rubygems.org,2010-01-19:Comment/153057742012-04-16T23:20:21Z2012-04-16T23:20:21ZHow to change platform of existing gem<div><p>If you're releasing a platform gem with JRuby then this is
wrong:</p>
<p><a href=
"https://github.com/pangloss/pacer/blob/develop/pacer.gemspec#L8">https://github.com/pangloss/pacer/blob/develop/pacer.gemspec#L8</a></p>
<p>If you use Gem::Platform::CURRENT it will set the platform
correctly for your packaged gem.</p></div>Eric Hodel