<indirect>
weaksauce: havenwood: the answer is "it depends, but probably not"
<indirect>
you can install all your gems into the same place
<indirect>
but you can have commands that aren't in your bundle that you want to run too
<indirect>
so always silently running bundle exec can be a good way to screw yourself over
<indirect>
eg if you run "rake routes | gist"
<indirect>
rake is in your bundle (and needs rails from in your bundle) but gist is not in your bundle, and needs to run outside it
<indirect>
so automatic bundle exec breaks that
<weaksauce>
yeah. that's the problem.
<indirect>
yup
<weaksauce>
I guess everyone just is religious with the bundle exec prefix then?
<indirect>
and there's no way to run a command in a shell that disables bundle exec
<indirect>
well you _could_ but you'd have to build it
<indirect>
weaksauce: I just bash alias b='bundle exec'
<indirect>
and then run "b rake | gist"
chouhoulis has quit [Remote host closed the connection]
<weaksauce>
not a bad idea
<havenwood>
indirect: good point, i shouldn't mention the caveats if I bring up rubygems-bundler
<havenwood>
:)
<havenwood>
i've gotten accustomed to it being quite common as part of default rvm these days
<indirect>
havenwood: I mean, rubygems-bundler _tries_ to avoid that problem
<indirect>
but when it doesn't work
<indirect>
it's a total fucking nightmare that's impossible to debug
<indirect>
basically
<havenwood>
yeah :O
<indirect>
because every rubygem executable is pre-fucked
<weaksauce>
yuck
<weaksauce>
b alias is probably better
martinisoft has quit [Quit: martinisoft]
samphippen has joined #bundler
shaileshg has quit [Quit: Connection closed for inactivity]
samphippen has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
woollyams has quit [Ping timeout: 252 seconds]
woollyams has joined #bundler
x1337807x has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
chouhoulis has joined #bundler
chouhoulis has quit [Ping timeout: 264 seconds]
woollyams has quit [Ping timeout: 252 seconds]
pipework has quit [Ping timeout: 264 seconds]
havenwood has quit [Remote host closed the connection]
havenwood has joined #bundler
havenwood has quit [Ping timeout: 255 seconds]
woollyams has joined #bundler
pipework has joined #bundler
samphippen has joined #bundler
woollyams has quit [Ping timeout: 252 seconds]
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
havenwood has joined #bundler
havenwood has quit [Ping timeout: 246 seconds]
<larshaugseth>
does anyone know if the 1.6 release is imminent? we could really use the source credentials in bundle config feature, but are loath to pull bundler off git in our prod environment.
samotarnik has joined #bundler
<samotarnik>
hi everyone. how do i start puma if i use "bundle install --deployment --binstubs"
<samotarnik>
*?
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
havenwood has joined #bundler
havenwood has quit [Ping timeout: 264 seconds]
cha1tanya has joined #bundler
ohwhoa has joined #bundler
cmmagid has joined #bundler
samotarnik has quit [Quit: Leaving]
ohwhoa has quit [Quit: woah!]
retro|cz has joined #bundler
ohwhoa has joined #bundler
tmoore has quit [Read error: Connection reset by peer]