[chef] Re: Re: Trouble with test-kitchen

[David Petzel < >]

Veewee is a Vagrant plugin and adds new sub-commands to Vagrant's command-line interface, similar to Knife (or RubyGems itself). When Vagrant runs, it searches the Ruby load path for plugins. You appear to have an older version of Veewee installed on your system already which isn't part of the bundle.

This is true, I do have veewee installed, as I had used this machine a while back to build some baseboxes for another project. I am not actually using it any longer, do you think removing it would help, or is the bundle approach the best path forward? 

What bundler gives you an isolated load path for the gems you execute with "bundle exec" in the context of the bundle - the gems installed and loaded in the Gemfile.lock. Since the bundle doesn't have veewee in it, Vagrant won't try and load it. It isn't intuitive at first, because we often just expect the software we install to work, but this kind of issue is one of the reasons why bundler exists in the first place.

Does that make sense?

At a high level it does make sense, but since I've never really look at bundler at GemSpec, there is a fair amount of mystery around it (until I read the docs on that stuff of course :) ) I'll certainly take some time and get up to speed on these and see how I make out.

Thanks again for taking the time to explain it.