From 5396c23308a42216d60ab0156846a17fe8061bb3 Mon Sep 17 00:00:00 2001 From: Stephanie Morillo Date: Thu, 20 Jul 2017 14:55:10 -0400 Subject: Added a sentence to `binstubs` Per feedback from @arbonap, we've added a sentence that briefly explains what binstubs is to the binstubs section. --- man/bundle-install.ronn | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/man/bundle-install.ronn b/man/bundle-install.ronn index d4bc34909a..0abfa97a4c 100644 --- a/man/bundle-install.ronn +++ b/man/bundle-install.ronn @@ -47,7 +47,12 @@ To apply any of `--deployment`, `--path`, `--binstubs`, or `--without` every time `bundle install` is run, use `bundle config` (see bundle-config(1)). * `--binstubs[=]`: - Creates a directory (defaults to `~/bin`) and place any executables from the + Binstubs are scripts that wrap around executables. Bundler creates a small Ruby + file (a binstub) that loads Bundler, runs the command, and puts it in `bin/`. + This lets you link the binstub inside of an application to the exact gem + version the application needs. + + Creates a directory (defaults to `~/bin`) and places any executables from the gem there. These executables run in Bundler's context. If used, you might add this directory to your environment's `PATH` variable. For instance, if the `rails` gem comes with a `rails` executable, this flag will create a -- cgit v1.2.1