17:59 <hotpancakes> I recently ran the "bundle package --all" command (in my rails app) to vendor gems into vendor/cache. Anyone know how to un-vendor gems?

18:09 <havenwood> hotpancakes: Check `bundle config` to see where `cache_all` is set so you can remove it. Or you could try: bundle config --local --unset cache_all

18:10 <hotpancakes> havenwood: I'm just getting "Settings are listed in order of priority. The top value will be used." when I run bundle config from the app's root dir. Anything I'm missing?

18:11 <havenwood> hotpancakes: There aren't any settings? Are you sure there's anything set?

18:12 <havenwood> hotpancakes: You might want to check your `.bundle/config` file.

18:13 <hotpancakes> havenwood: I believe I actually removed the .bundle directory in trying to un-vendor.

18:13 <havenwood> hotpancakes: Aha

18:14 <hotpancakes> havenwood: but bundler is still using the vendored gems. In my case, do I just purge the dir?

18:14 <havenwood> hotpancakes: Yeah, as far as I know there's not a command for that.

18:14 <hotpancakes> havenwood: Not a problem. I was just trying to avoid shooting myself in the foot.

18:15 <havenwood> :)

18:15 <hotpancakes> havenwood: Thanks for the help! :)

18:15 <havenwood> hotpancakes: You're welcome, no prob.

19:45 <kwstannard> I have a question that I can't find an answer to. Say I have a dependency graph that looks like this: App -> FooGem -> BarGem. All three are cloned into my local machine. Is there an easy way to tell inform bundler that when I bundle on App, that I want to use the local BarGem repository instead of the remote source?

19:46 <kwstannard> And to do it in a way that doesn't break encapsulation of FooGem by telling the App Gemfile that there is a BarGem.