On 10/15/07, Luis Lavena <[EMAIL PROTECTED]> wrote: > The current and beta versions of RubyGems suffer from a location > specific problem: > > Installing RubyGems (ruby setup.rb install) will mark the .cmd to a > specific path (Gem.ruby) which will brake if user move the folder > around (or during creation of installer like One-Click installer). > > Also, installing gems create stubs that call the same ruby executable > (Gem.ruby) and the script "without path", which is broken (since it > will try to locate "script" in the current directory). > > http://pastie.caboo.se/107250 > > This patch provides a "naive" solution to the problem, using the ruby > installation where the stub is located, and also using the > extension-less ruby script. > > As shown in the stub script, there is a door open to provide a > workaround for win9x, but I didn't (since I commented on previous > post: lack the installation to try it).
This may sound callous, but if you're not running at least Win2k, you're not running a Windows worth worrying about. There's too many features missing from command.com to make for a viable Ruby installation for most people to use. (No PATHEXT, no FTYPE, only .bat and not .cmd.) It would also be pretty easy to substitute the appropriate values at install-time rather than relying on cmd.exe variable substitution tricks. -austin -- Austin Ziegler * [EMAIL PROTECTED] * http://www.halostatue.ca/ * [EMAIL PROTECTED] * http://www.halostatue.ca/feed/ * [EMAIL PROTECTED] _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
