Bugs item #28414, was opened at 2010-07-22 05:44 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28414&group_id=126
Category: `gem` commands (other) Group: v1.3.x >Status: Closed >Resolution: Out of Date Priority: 3 Submitted By: Svetoslav Agafonkin (svetlyo) Assigned to: Eric Hodel (drbrain) Summary: RubyGems 1.3.7 default gem directory is wrong when used with ruby 1.9.1 with --program-suffix=1.9 Initial Comment: RubyGems 1.3.7 default gem directory is wrong when used with ruby 1.9.1 with --program-suffix=1.9. Gem.default_dir generates "/opt/local/lib/ruby/gems/1.9.1/" instead of "/opt/local/lib/ruby1.9/gems/1.9.1/". The change was introduced in lib/rubygems/defaults.rb in http://github.com/rubygems/rubygems/commit/0495c7c0dd9878f9a7a74f5133d7892d28d01812 - a big import from the ruby trunk, right after 1.3.6 was released. The original change comes from this commit: http://redmine.ruby-lang.org/repositories/diff/ruby-19?rev=26048 --------------------- Mac OS X 10.5.8 ruby 1.9.1_429 (from Macports) rubgygems 1.3.7 $ gem1.9 env RubyGems Environment: - RUBYGEMS VERSION: 1.3.7 - RUBY VERSION: 1.9.1 (2010-07-02 patchlevel 429) [i386-darwin9] - INSTALLATION DIRECTORY: /opt/local/lib/ruby/gems/1.9.1 - RUBY EXECUTABLE: /opt/local/bin/ruby1.9 - EXECUTABLE DIRECTORY: /opt/local/bin - RUBYGEMS PLATFORMS: - ruby - x86-darwin-9 - GEM PATHS: - /opt/local/lib/ruby/gems/1.9.1 - /Users/fro/.gem/ruby/1.9.1 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://rubygems.org/ ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-06-21 16:18 Message: I'm closing this ticket as we've moved to github issues for all issue tracking. Please refile this ticket there if you think it is still valid. https://github.com/rubygems/rubygems/issues Thanks, The RubyGems Team ---------------------------------------------------------------------- Comment By: Ryan Davis (zenspider) Date: 2011-06-07 16:50 Message: Hi! Believe it or not, we're moving to github's issue tracker! The pressure to move has been loud and clear, but for the longest time it didn't support the way we worked. Now that it has freeform labels it can support our workflow adequately. There is just one problem: Your bug is here and we don't want to lose you! What we'd like you to do is fairly painless and should only take a few minutes: Please file the _exact_ same ticket on github and provide a link back to this crufty old ticket so we can refer to any previous discussion that occurred. Once the new ticket is made, put a forwarding link to it here and close this ticket out. In a couple weeks, we'll track down the old tickets that are still open and decide what to do with them. We could have done this fairly automatically, but we really want you to do it so you're attached to the ticket and we can still communicate with you and keep a record of it. https://github.com/rubygems/rubygems/issues Thanks, The RubyGems Team ---------------------------------------------------------------------- Comment By: James Tucker (raggi) Date: 2010-11-13 08:20 Message: This is also related to a ruby bug that I need to submit. Feel free to assign to me after the we decide what to do with the suffix. ---------------------------------------------------------------------- Comment By: John Barnette (jbarnette) Date: 2010-11-13 05:44 Message: Eric, what do you think? ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=575&aid=28414&group_id=126 _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
