00:27 <ntucker_> any advice on debugging why bundler is using the wrong version of ruby to attempt to install my gems under rbenv?

00:28 <ntucker_> i have ruby 1.8.7 installed under rbenv and that is working fine for running my apps, but if i attempt to use bundler, i get errors about gems failing to install and the stacktraces indicate that it's trying to install them with ruby 2.0 (default from the system, a brand new OSX machine)

00:29 <ntucker_> this makes sense, as many of the gems in this project are not compatible with ruby 2.0, which is the reason for the rbenv'ing

00:33 <ntucker_> aha, i just discovered that /usr/bin/bundle has a hardcoded #!/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby

00:33 <ntucker_> is that intentional/desirable?

00:36 <ntucker_> aha aha: when i did a 'sudo gem install bundler' i became root and lost my rbenv env. doing a sudo -E gem install bundler solves the prob

09:28 <ntucker_> hi bundlers. i have an internally hacked version of the mysql2 gem that is checked into an SVN repo as a .gem file and I'd like to figure out a way to install it with bundler. As best as I can figure out is that i need to unpack the .gem file into a directory containing a gemspec and then I can refer to it in my Gemfile with :path => path/to/dir/containing/gemspec

09:29 <ntucker_> when i do this, bundle install appears to succeed, but then i'm unable to require 'mysql2'. it gives me the error: ... neal-devsetup/btest/mysql2-0.3.12b5/lib/mysql2.rb:8:in `require': no such file to load -- mysql2/mysql2 (LoadError)

09:31 <ntucker_> so it would appear that bundler can find the initial file (msyql2-0.3.12b5/lib/mysql2.rb) but that 'require' calls inside it do not work properly (there is a "require 'mysql2/mysql2/'" in that file which works if I install the gem via 'gem install' rather than with bundler

09:32 <ntucker_> i'm not sure how to proceed debugging this. any advice would be appreciated

09:33 <ntucker_> it's possible that i've totally misunderstood how i'm supposed to go about bundling a gem from sources

09:41 <ntucker_> more data: if i make a local gem server containing only that gem and use :source => 'http://localhost:8808' in my Gemfile it works ok. So it's simply something to do with how I am referring to it in the Gemfile

09:52 <ntucker_> oh, hmm, it seems that 'bundle install' is not actually building the C parts of this gem. obviously i'm misunderstanding something