Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

default $LOAD_PATH is include /tmp/ruby/ ? #71

Open
zw963 opened this issue Mar 5, 2016 · 1 comment
Open

default $LOAD_PATH is include /tmp/ruby/ ? #71

zw963 opened this issue Mar 5, 2016 · 1 comment

Comments

@zw963
Copy link

zw963 commented Mar 5, 2016

following is a test for traveling-ruby package.

#!/usr/bin/env ruby
# -*- coding: utf-8 -*-

puts "Ruby Version: #{RUBY_VERSION} #{RUBY_PLATFORM}"
puts "LOAD_PATH:"
puts $:
~/121/hello-1.0.0/linux-x86_64/hello
Ruby Version: 2.2.2
Ruby PLATFORM: x86_64-linux
LOAD_PATH:
/home/zw963/121/hello-1.0.0/linux-x86_64/lib/ruby/lib/ruby/site_ruby/2.2.0
/home/zw963/121/hello-1.0.0/linux-x86_64/lib/ruby/lib/ruby/site_ruby/2.2.0/x86_64-linux
/home/zw963/121/hello-1.0.0/linux-x86_64/lib/ruby/lib/ruby/site_ruby
/home/zw963/121/hello-1.0.0/linux-x86_64/lib/ruby/lib/ruby/vendor_ruby/2.2.0
/home/zw963/121/hello-1.0.0/linux-x86_64/lib/ruby/lib/ruby/vendor_ruby/2.2.0/x86_64-linux
/home/zw963/121/hello-1.0.0/linux-x86_64/lib/ruby/lib/ruby/vendor_ruby
/home/zw963/121/hello-1.0.0/linux-x86_64/lib/ruby/lib/ruby/2.2.0
/home/zw963/121/hello-1.0.0/linux-x86_64/lib/ruby/lib/ruby/2.2.0/x86_64-linux
/tmp/ruby/lib/ruby/site_ruby/2.2.0
/tmp/ruby/lib/ruby/site_ruby/2.2.0/x86_64-linux
/tmp/ruby/lib/ruby/site_ruby
/tmp/ruby/lib/ruby/vendor_ruby/2.2.0
/tmp/ruby/lib/ruby/vendor_ruby/2.2.0/x86_64-linux
/tmp/ruby/lib/ruby/vendor_ruby
/tmp/ruby/lib/ruby/2.2.0
/tmp/ruby/lib/ruby/2.2.0/x86_64-linux

I have unset all my ruby environment variable, RUBYOPT, RUBYLIB.
still see /tmp/ruby/lib..., this is so strange ...

@FooBarWidget
Copy link
Member

That's because in our build environment Ruby is compiled against the prefix /tmp/ruby. This is normal. We should have a way in some future release to remove that default path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants