Bug 1100840

Created attachment 898709 [details]
removes hard coded native lib path

Description of problem:
It's possible to use rubygem-passenger in multiple Ruby environments by rebuilding it for other SCLs or as a non-SCL RPM, but currently the RHSCL SRPM carries a patch that hardcodes the native library path.

$ grep -A2 "def load_from_load_path" ./opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/native_support.rb
	def load_from_load_path
		require "/opt/rh/ruby193/root/usr/lib64/gems/exts/passenger-4.0.18/lib/native/#{library_name}"
		return true

When changing the Ruby environment using the PassengerRuby directive that the preloader will always load the ruby193 variant irrespective of which ruby interpreter it's running under and which load paths are set.

Attached is a patch that makes it rely properly on the load path instead of being hardcoded, so is compatible with multiple Ruby envs.

The patch also patches the gemspec so the Fedora/RHSCL rubygems package's custom 'exts' load path is added.

It'd be appreciated if this can be sent upstream to Fedora too if it's accepted here.

Version-Release number of selected component (if applicable):
ruby193-rubygem-passenger-4.0.18-10.el6

How reproducible:
Always

Steps to Reproduce:
1. Rebuild SRPM for an additional SCL, e.g. ruby200 (or non-SCL, but that's harder)
2. Install both sets of RPMs, but only ruby193-mod_passenger (only one Apache module is needed)
3. Create single command wrappers to launch ruby193 or ruby200 (https://github.com/maxamillion/ruby-wrapper)
4. Define two VirtualHosts, one with PassengerRuby /usr/bin/ruby193-ruby, the other with PassengerRuby /usr/bin/ruby200-ruby
5. Verify using RUBY_VERSION inside each, or "ps" that they're both loaded under different interpreters successfully