22:04 <_73> Hello. I am creating a Perl "Alien" for Ruby, which is a Perl module that that when installed will build and install Ruby into a private share location. Please note that I compile this Ruby with the "--enable-load-relative" flag. Anyways, when I try to use the "gem" program that comes with this ruby, to install a gem into a custom directory using the "--install-dir" option, I am having erroneus shebang-related issues such that the

22:04 <_73> installed gem wont execute. Here is an example of me trying to use the fpm gem after successfully installing it: http://dpaste.com/9UYQZR5JT . I made an annotation in this output (prefixed by ### _73:), that the correct and desired ruby shebang line is present in the file, but it is being overridden by the "$bindir/ruby" binstub (I think binstub is the correct term?). So my question is, how could I make sure that the shebang line in my

22:04 <_73> installed gem points to the ruby that was used to run "gem" in the first place?

22:40 <adam12> _73: Hmm weird.

22:41 <adam12> _73: Running that binary directly works tho? Only thing I cn think of is you're running afould of the linux binary loader and that's not a binary.

22:46 <_73> The ruby binary works. So does the "gem" program that came with it. The gems I install with it (in this case fpm) do not work, unless I manually pass them to ruby. Here is the output of running "file" against the ruby binary: http://dpaste.com/733WFLUQS

22:47 <adam12> Hmm

22:48 <_73> I certainly find it curious that the correct shebang line is present in this fpm gem, but is being overriden.

23:19 <_73> hmm I think I re-discovered this issue: https://github.com/rubygems/rubygems/issues/2955

23:19 <_73> I may be able to work around this by using bundle instead of gem, since I can use its --shebang option