Bug #1941
Issues with Ruby 1.8.6 patchlevel 383 and any package installation
| Status: | Assigned | Start date: | 08/16/2009 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | - | |||
| Target version: | - | |||
| ruby -v: | ruby 1.8.6 (2009-08-04 patchlevel 383) [i386-mingw32] |
Description
Working on updating RubyInstaller packages to recently released patchlevel 383, found that my patching strategies over rbconfig no longer works. On previous patchlevel (368), I configure ruby with my sandbox path, and once installed, gsub it from rbconfig, leaving this: CONFIG["prefix"] = (TOPDIR || DESTDIR + "") Where my path was inside "". Since TOPDIR refers to rbconfig.rb itself (but with stripped path), prefix end being always the path where Ruby ends installed/copied. DESTDIR ends not being used for the prefix, and it's value turns to be "C:" Now, bear with me for a second, on p368: CONFIG["libdir"] = "$(exec_prefix)/lib" CONFIG["exec_prefix"] = "$(prefix)" But on p383: CONFIG["exec_prefix"] = "$(DESTDIR)" This affects installation of rubygems and packages that uses setup.rb Other places that uses $(DESTDIR) instead of previous values: CONFIG["sitedir"] = "$(DESTDIR)/lib/ruby/site_ruby" Wonder why the change, if DESTDIR was not used during make, why remove the usage of prefix on this case? Thank you.
History
Updated by wyhaines (Kirk Haines) over 2 years ago
- Status changed from Open to Assigned
Updated by luislavena (Luis Lavena) almost 2 years ago
At patchlevel 398 we changed our patching strategy: http://github.com/oneclick/rubyinstaller/blob/master/recipes/interpreter/ruby18.rake#L124-125 While is still unclear for me the purpose of above change, our patching solved our problem. Thank you.