From 1b6646165b8c1bbaa06656f8937a5348caacb9f6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20Ho=CC=88ltje?= Date: Fri, 15 Jul 2016 13:49:10 -0400 Subject: [PATCH] readme: Removed what it is doing section I don't understand that readme language and I wrote the plugin! I think the shell code is actually clear enough that anyone who was interested can look at it themselves. --- README.md | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/README.md b/README.md index af6e9e6..06a7c1b 100644 --- a/README.md +++ b/README.md @@ -51,27 +51,6 @@ If you are having problems, try running `sanity-check.sh`: $ $SHELL "$(rbenv root)/plugins/rbenv-chefdk/sanity-check.sh" ``` -What rbenv-chefdk is doing... ------------------------------ - -rbenv-chefdk modifies `rbenv which` and `rbenv rehash` to search for -executables in: - -1. `~/.chefdk/gem/ruby//bin` -- When you install gems in - ChefDK, this is where gems are installed when using the ChefDK. -2. `/opt/chefdk/bin` -- These are the normal commands for using chef. -3. `/opt/chefdk/embedded/bin` -- This is only added to `rbenv which` and - partially to `rbenv rehash`. Some of the commands here would break your - system if shims were created for them. -4. `/opt/chefdk/embedded/lib/ruby/gems//bin` -- These are - the gems that ChefDK pre-installed for you. - -The `rbenv which` command is used by all the internal rbenv plumbing, including -the shims and `rbenv exec`. - -The `rbenv rehash` command generates the shims you are actually using when you -run a command that came with ruby or a gem. - Frequently Asked Questions --------------------------