[chef] Re: Trouble with test-kitchen

[Joshua Timberman < >]

Hi David!

On Aug 18, 2012, at 7:17 AM, David Petzel 
<
 >
 wrote:

> Out of curiosity, why is veewee even loaded? I'm simply running the tests 
> against existing baseboxes. As I understand veewee is simply for 
> automatting the creation of new baseboxes, If we are not creating a new 
> one, does veewee really need to load? Or is this just a byproduct of way 
> its included (Again please bear with my ruby 'noobness', if this is a dumb 
> question)

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.

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?

-- 
Opscode, Inc
Joshua Timberman, Technical Program Manager
IRC, Skype, Twitter, Github: jtimberman