incorrect base_dir for default gemspecs
gemspecs for default gems have incorrect path since they're installed in a subdirectory of the normal specifications path. The base_dir is dirname(dirname(loaded_from)), so using an additional subdir results in a base_dir that's "off by one." Example:
Find the gemspec for the default rake gem:
spec = Gem::Specification.find_by_name('rake')
=> #<Gem::Specification:0x3fc3fa4dd570 rake-0.9.5>
The spec.base_dir should be "/Users/jeremy/.rbenv/versions/2.0.0-preview2/lib/ruby/gems/2.0.0"
This means Gem.bin_path lookups in bin/rake, etc result in incorrect executable paths:
Updated by luislavena (Luis Lavena) over 10 years ago
- Status changed from Open to Assigned
- Assignee set to drbrain (Eric Hodel)
Updated by drbrain (Eric Hodel) over 10 years ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
This issue was solved with changeset r38229.
Jeremy, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
lib/rubygems/package.rb: Set rubygems_version before validation.
Fixes issue with bundler.
test/rubygems/test_gem_package.rb: Test for above.
lib/rubygems/remote_fetcher.rb: Only update the cache when we have
permission. [ruby-trunk - Bug #7509]
lib/rubygems/source.rb (class Gem): ditto
test/rubygems/test_gem_remote_fetcher.rb: Test for above.
lib/rubygems/specification.rb: Derive base_dir properly for default
gems. [ruby-trunk - Bug #7496]
test/rubygems/test_gem_specification.rb: Test for above.
lib/rubygems.rb: Untaint Dir.pwd when searching for gemdeps files
for operation under $SAFE=1
Updated by bitsweat (Jeremy Daer) over 10 years ago