Bug #4485
closed
Gem.bin_path('rake') does not return the path of the system-installed rake
Added by erikh (Erik Hollensbe) over 13 years ago.
Updated over 13 years ago.
Description
=begin
Please see subject. You can see this evident in rubygems-test version 0.3.8 and lower, where bin_path is used to retrieve the rake path. In systems where a suffix is appended to the ruby version (e.g., ruby19/rake19/gem19), you will see that it is unable to locate the path via bin_path.
=end
Files
- Status changed from Open to Assigned
- Assignee set to drbrain (Eric Hodel)
- Target version set to 1.9.3
The attached patch adds executables to the stub gemspecs and installs a copy of bin/rake into the gem directory.
Can I have it reviewed?
Nobu, please review Eric's patch soon. We don't have much time.
- ruby -v changed from 1.9.2 to -
Hi,
At Sat, 9 Jul 2011 08:47:13 +0900,
Eric Hodel wrote in [ruby-core:37902]:
The attached patch adds executables to the stub gemspecs and installs a copy of bin/rake into the gem directory.
It seems a half of the path is unconcerned in this issue but
just renaming of a local variable, right?
In the last part, it could be simply:
execs = execs.map {|exec| File.join(srcdir, 'bin', exec)}
install(execs, bin_dir, :mode => $prog_mode)
Totally, it seems nice.¶
Nobu Nakada
The install of tool/rbinstall.rb only allows one source item per call so I couldn't take full advantage of your suggestion.
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0Like0