binstubs don't actually work about heroku-buildpack-ruby

[nicholasmott]

After running through the build pack I found the following quite confusing relating to binstubs. It may just be my lack of experience but it seemed the buildpack was doing the following.

• Installing Ruby into ../vendor/ruby-x.x.x
• Symlinking from ../vendor/ruby-x.x.x/bin to ../bin
• Bundled binstubs to ../vendor/bundle/bin
• Symlinking from ../vendor/bundle/ruby/x.x.x/bin to ../bin without overwriting anything already there
• Doesn't actually appear to symlink vendor/bundle/bin anywhere although the actual list of binstubs in ../vendor/bundle/ruby/x.x.x/bin seems to be the same as you would expect from your gemfile

I couldn't work out how gem binstubs were actually added to ../vendor/bundle/ruby/x.x.x/bin although the binstubs here are generated by rubygems so I may be missing a gem install somewhere.

The binstubs themselves in ../vendor/bundle/ruby/x.x.x/bin are different than those in vendor/bundle/bin, they are generated by rubygems rather than bundler.

An example impact of this sequence of events is rake. By symlinking from the ruby install you get rake 0.9.2.2 regardless of what version of rake you may have in your gemfile. If other gems rely on a later version of rake you may get hard to track down errors and failures.

The larger issue, of course, is that binstubs are not actually run in the context of the gemfile and bundler seems to be cut out of the process altogether.

[schneems]

Is this still an issue?