glennpratt has quit [Remote host closed the connection]
Cidan has quit [Ping timeout: 252 seconds]
c355e3b has quit [Quit: Connection closed for inactivity]
Cidan has joined #bundler
glennpratt has joined #bundler
glennpratt has quit [Remote host closed the connection]
glennpratt has joined #bundler
glennpratt has quit [Remote host closed the connection]
igitoor_ has joined #bundler
headius_ has joined #bundler
sonalkr1- has joined #bundler
sonalkr132 has quit [*.net *.split]
headius has quit [*.net *.split]
igitoor has quit [*.net *.split]
igitoor_ has quit [Changing host]
igitoor_ has joined #bundler
igitoor_ is now known as igitoor
c355e3b has joined #bundler
glennpratt has joined #bundler
glennpratt has quit [Remote host closed the connection]
glennpratt has joined #bundler
glennpratt has quit [Remote host closed the connection]
glennpratt has joined #bundler
glennpratt has quit [Remote host closed the connection]
glennpratt has joined #bundler
glennpratt has quit [Remote host closed the connection]
gkop has joined #bundler
<gkop>
Hi there, is this the best way to check if a gem is currently bundled/available after Bundler.require() (context is the gem has require: false in Gemfile) ? Bundler.definition.index.search("rspec-core")
<gkop>
Or is there a higher-level API that will be more resilient to changes in Bundler? (it's not clear that ^^ is public API)
<gkop>
Would I be better off asking Gem?
<gkop>
eg. Gem.loaded_specs["rspec-core"]
glennpratt has joined #bundler
glennpratt has quit [Ping timeout: 260 seconds]
djbkd has joined #bundler
glennpratt has joined #bundler
ntucker_ has joined #bundler
ntucker has quit [Ping timeout: 252 seconds]
glennpratt has quit [Ping timeout: 240 seconds]
glennpratt has joined #bundler
glennpratt has quit [Ping timeout: 240 seconds]
glennpratt has joined #bundler
glennpratt has quit [Remote host closed the connection]