Hello everybody, While working on RubyInstaller project, we found that version 1.2 included a --destdir option during the installation procedure (setup.rb).
This new option, introduced several problems during setup for us, that I and Eric fixed in the repository. We found in RubyInstaller that using --prefix to install rubygems outside ruby installation (for packaging process) was not clean enough. destdir option was more appropriate. The thing is destdir was not clever enough to detect paths with drive letters, so we ended with a broken installation attempt. To workaround this, Gordon Thiesfeld pointed me to the usage of RbConfig::TOPDIR and leverage in Pathname to compute the path relatives. The following patch fixes the two install_destdir occurrences: http://pastie.org/private/22dli3cc6lg0blmqzumda Disregard the FIXME legend since do not apply, mainly because using Pathname to compute the relative path we solve the drive letters :-) Since the install_destdir code and functionality resides into setup.rb, there is no testing mechanism for it. Can the original author that proposed the destdir functionality review this patch? I didn't had chance to test it on other platforms besides Windows. Thanks in advance and looking forward for the comments. -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
