Hi guys, I'm trying to do the final round of patches, and be less noisy about them. Please excuse if I added to you too much work on this.
As Curt, Nobu, Eric and Daniel stressed on ruby-forum, ruby-talk and this list too, the use of .cmd files over .bat ones is a bit problematic. We have two kind of scripts stubs (the bat/cmd files that actually launch ruby with the script): - The ones set when rubygems is installed in your ruby installation (setup.rb) - The ones that rubygems create when installing/updating gems (installer.rb) Also, there are two problems with setup.rb and installer.rb: - The path to the ruby installation (Gem.ruby) is fixed. (That means you cannot relocate your ruby from c:/ruby to d:/ruby without requiring manually update all those .bat/.cmd files). - The pathless calling of the script: @"C:/Ruby/bin/ruby.exe" "gem" %* That is wrong... that only will work if current directory (pwd) is C:/Ruby/bin/ The patches I provided in the RubyForge tracker provide a solution for this, but I was using the .cmd extension for those file. Now, taking in consideration the comment from Eric at ruby-talk, those scripts should be .bat instead, since PATHEXT takes preference for them instead of .cmd ones: D:\Users\Developer\code>set PATHEXT PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH So, I'm about to provide the final round of patches to this topic, with the following considerations: - All the stub scripts generated by setup.rb and installer.rb will be .bat files. - The stubs will evaluate WinNT/Win9x scenario and use the extension power available in the NT platform or stick to a prefixed path for win9x. - Add more comments to the stubs generated and the methods defined for them. Any suggestion? objections? Thanks again for the opportunity and the openness to accept those patches into RubyGems. -- 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 _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
