Sorry guys.
I just found that we -- well, actually I -- missed a few .cmd
extensions when uninstalling some gems.
Since there wasn't testing for uninstall process, that didn't popped :-P
Again, sorry to just found it, I was too focused on getting everything
working that never tried to uninstall a gem.
Attached is a simple patch that correct the bad behavior.
Regards and good weekend,
--
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
Index: lib/rubygems/installer.rb
===================================================================
--- lib/rubygems/installer.rb (revision 1478)
+++ lib/rubygems/installer.rb (working copy)
@@ -180,7 +180,7 @@
end
##
- # Creates windows .cmd files for easy running of commands
+ # Creates windows .bat files for easy running of commands
#
def generate_windows_script(bindir, filename)
if Gem.win_platform? then
Index: lib/rubygems/uninstaller.rb
===================================================================
--- lib/rubygems/uninstaller.rb (revision 1478)
+++ lib/rubygems/uninstaller.rb (working copy)
@@ -95,7 +95,7 @@
gemspec.executables.each do |exe_name|
say "Removing #{exe_name}"
File.unlink File.join(Gem.bindir, exe_name) rescue nil
- File.unlink File.join(Gem.bindir, exe_name + ".cmd") rescue nil
+ File.unlink File.join(Gem.bindir, exe_name + ".bat") rescue nil
end
end
end
_______________________________________________
Rubygems-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers
