Hardcoded "opscode" path

[dandv]

I've just installed ChefDK on Windows in a directory I chose, and vagrant up died with :

Bringing machine 'default' up with 'virtualbox' provider...
The following berks command failed to execute:

    C:\utils\chef\chefdk\bin/berks.BAT --version --format json

The stdout and stderr are shown below:

    stdout:
    stderr: C:/Utils/chef/chefdk/bin/berks:38:in `load': cannot load such file -- C:/opscode/chefdk/embedded/apps/berkshelf/bin/berks (LoadError)
        from C:/Utils/chef/chefdk/bin/berks:38:in `<main>'

I replaced opscode with the actual path in all files under bin, but I still get errors:

C:\Vagrant\meteor>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
    default: The Berkshelf shelf is at "C:/Users/A/.berkshelf/vagrant-berkshelf/shelves/berkshelf20141130-6800-1yco55z-default"
==> default: Sharing cookbooks with VM
There are errors in the configuration of this machine. Please fix
the following errors and try again:

Berkshelf:
* berksfile_path must be set

If opscode is the only directory that works, then maybe an option would be to remove the directory choice from the install wizard.

PS: I'm new to Berkshelf; please file the issue appropriately if this is the wrong place.

[sethvargo]

Looks like a vagrant-berkshelf issue, but that path is not hard coded. /cc @danielsdeleo

[danielsdeleo]

Yeah, this is a dup of this one: chef-boneyard/chef-dk#68 @sethvargo you can probably close as an upstream bug (or however you like to deal with those).

@dandv the issue is currently fixed in master and we've verified that some test builds work. The next release of ChefDK will include the fix for this.

[sethvargo]

@danielsdeleo thanks! Labeled as an upstream bug for history.