06:32 <tabakhase> hu, what _exacly_ is Bundler.require supposed to do? - it kinda reads like it removes my need to require 'redis' for example when my gemspec has it as runtimeDep. -- but it seems like thats not actually what it is

06:34 <tabakhase> kinda same questions follows up to the Bundler.setup // if i do that in my executable - my examples say yes, my understanding kinda says no...

06:35 <tabakhase> and last, if its in there, shouldnt bundler not just be a dev_depend in my gemspec but a runtime_ so everyone gets it?

06:36 <tabakhase> last two quests are kinda one

06:37 <tabakhase> very basic questions, but im new to ruby and struggle in getting just the structural basis right =) so any pinpoints / things i should read are welcome

06:48 <julienk> what is the difference between bundle exec myexec

06:48 <julienk> of directly launching myexec

06:48 <julienk> ?

06:51 <tabakhase> (me bloody noob) -- run "bundler exec env" and "env" and compare the putputs for a start julienk

07:02 <julienk> @tabakhase

07:02 <julienk> I did it

07:03 <tabakhase> so you see RUBYOPT and RUBYLIB poping up new, any more changes ;D

07:03 <julienk> I see that for bundler env the PATH has been prepended with the rubygem binary and that RUBYOPT and RUBYLIB env variable are included also

07:04 <julienk> so basically...bundler exec something just executes the binary but with different environment variables?

07:16 <tabakhase> yep, with making sure its the ones bundler install shipped

07:16 <tabakhase> and docu says "some/a lot" might/will work without needing bundler exec * call

07:17 <tabakhase> guess that depends then on other gems/version of the gem someone has installed on his box or so..

07:17 <tabakhase> but thats just observation, not knowledge....

07:20 <julienk> ok thx :)

09:27 <jhass> julienk: another way of thinking about it is that it prepends require "bundler/setup" to your script