You have to set your paths by running
chef shell-init (with the correct eval for your particular shell) for things to work correctly. If you have installed chef-client, berks, kitchen, etc. via rubygems and you have rvm’s bin dir first in your path, your shell will pick up the rvm versions. I think there’s a way now to switch rvm to chefdk, but I don’t use rvm so I don’t know what that is.
On Friday, September 11, 2015 at 11:43 AM, niristotle okram wrote:
i just did and now i get these errors
± |master ✗| → chef -v
Chef Development Kit Version: 0.6.0
chef-client version: ERROR
berks version: ERROR
kitchen version: ERROR
Are they because of the PATH
On Fri, Sep 11, 2015 at 11:38 AM, Daniel DeLeo <firstname.lastname@example.org (mailto:email@example.com)> wrote:
Just install the new package on top of the old one
On Friday, September 11, 2015 at 11:27 AM, niristotle okram wrote:
Hey guys, i have been looking for an answer to this possibly a dumb question.
Whats the procedure to upgrade the chefdk? Google returns steps to install but not for upgrading an existing install. I would assume now, that to upgrade, one have to follow the installation procedure. IS this right? I am trying to upgrade from the 0.3.5 to 0.6.0