Project

General

Profile

Actions

Bug #3805

closed

Ruby generated gem specifications for bundled projects are incorrect

Added by luislavena (Luis Lavena) over 13 years ago. Updated almost 13 years ago.

Status:
Closed
Assignee:
-
Target version:
ruby -v:
ruby 1.9.3dev (2010-09-09 trunk 29199) [x86_64-darwin10.4.0]
Backport:
[ruby-core:32165]

Description

=begin
Hello,

One porblem with found with Ruby 1.9.2 and current trunk is that during installation, the generated gem specifications are incomplete and lack the versioned file information needed for a successful gem install.

One common problem is the installation of rake itself. See the following git for the full list of commands:

http://gist.github.com/570419

After doing gem install rake, rake doesn't work:


 $ rake --version
 rake, version 0.8.7
 
 $ gem install rake
 Successfully installed rake-0.8.7
 1 gem installed
 
 $ rake --version
 /Users/luis/.portile/apps/x86_64-apple-darwin10.4.0/ruby/1.9.3-trunk/lib/ruby/1.9.1/rubygems.rb:340:in `bin_path': can't find executable rake for rake-0.8.7 (Gem::Exception)
 	from /Users/luis/.portile/apps/x86_64-apple-darwin10.4.0/ruby/1.9.3-trunk/bin/rake:19:in `'
 

This issue is solved by removing the non-versioned .gemspec files (or actually renaming them with version.

Attached is a patch that adds the version to the gemspec in rbinstall script.

With it applied:


 $ rake --version
 /Users/luis/.portile/apps/x86_64-apple-darwin10.4.0/ruby/1.9.3-trunk/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake/alt_system.rb:32: Use RbConfig instead of obsolete and deprecated Config.
 rake, version 0.8.7
 

This change should also be backported into 1.9.2 branch.

Thank you.
=end


Files

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0