bundler 1.16.1 → 1.17.3

data/man/bundle-config.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-CONFIG" "1" "December 2017" "" ""
+.TH "BUNDLE\-CONFIG" "1" "December 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-config\fR \- Set bundler configuration options
@@ -10,7 +10,24 @@
 \fBbundle config\fR [\fIname\fR [\fIvalue\fR]]
 .
 .SH "DESCRIPTION"
-This command allows you to interact with bundler\'s configuration system\. Bundler retrieves its configuration from the local application (\fBapp/\.bundle/config\fR), environment variables, and the user\'s home directory (\fB~/\.bundle/config\fR), in that order of priority\.
+This command allows you to interact with Bundler\'s configuration system\.
+.
+.P
+Bundler loads configuration settings in this order:
+.
+.IP "1." 4
+Local config (\fBapp/\.bundle/config\fR)
+.
+.IP "2." 4
+Environmental variables (\fBENV\fR)
+.
+.IP "3." 4
+Global config (\fB~/\.bundle/config\fR)
+.
+.IP "4." 4
+Bundler default config
+.
+.IP "" 0
 .
 .P
 Executing \fBbundle config\fR with no parameters will print a list of all bundler configuration for the current bundle, and where that configuration was set\.
@@ -63,7 +80,7 @@ A space\-separated list of groups referencing gems to skip during installation\.
 A space\-separated list of groups referencing gems to include during installation\.
 .
 .SH "BUILD OPTIONS"
-You can use \fBbundle config\fR to give bundler the flags to pass to the gem installer every time bundler tries to install a particular gem\.
+You can use \fBbundle config\fR to give Bundler the flags to pass to the gem installer every time bundler tries to install a particular gem\.
 .
 .P
 A very common example, the \fBmysql\fR gem, requires Snow Leopard users to pass configuration flags to \fBgem install\fR to specify where to find the \fBmysql_config\fR executable\.
@@ -98,7 +115,7 @@ After running this command, every time bundler needs to install the \fBmysql\fR
 Configuration keys in bundler have two forms: the canonical form and the environment variable form\.
 .
 .P
-For instance, passing the \fB\-\-without\fR flag to [bundle install(1)][bundle\-install] prevents Bundler from installing certain groups specified in the Gemfile(5)\. Bundler persists this value in \fBapp/\.bundle/config\fR so that calls to \fBBundler\.setup\fR do not try to find gems from the \fBGemfile\fR that you didn\'t install\. Additionally, subsequent calls to [bundle install(1)][bundle\-install] remember this setting and skip those groups\.
+For instance, passing the \fB\-\-without\fR flag to bundle install(1) \fIbundle\-install\.1\.html\fR prevents Bundler from installing certain groups specified in the Gemfile(5)\. Bundler persists this value in \fBapp/\.bundle/config\fR so that calls to \fBBundler\.setup\fR do not try to find gems from the \fBGemfile\fR that you didn\'t install\. Additionally, subsequent calls to bundle install(1) \fIbundle\-install\.1\.html\fR remember this setting and skip those groups\.
 .
 .P
 The canonical form of this configuration is \fB"without"\fR\. To convert the canonical form to the environment variable form, capitalize it, and prepend \fBBUNDLE_\fR\. The environment variable form of \fB"without"\fR is \fBBUNDLE_WITHOUT\fR\.
@@ -107,7 +124,7 @@ The canonical form of this configuration is \fB"without"\fR\. To convert the can
 Any periods in the configuration keys must be replaced with two underscores when setting it via environment variables\. The configuration key \fBlocal\.rack\fR becomes the environment variable \fBBUNDLE_LOCAL__RACK\fR\.
 .
 .SH "LIST OF AVAILABLE KEYS"
-The following is a list of all configuration keys and their purpose\. You can learn more about their operation in [bundle install(1)][bundle\-install]\.
+The following is a list of all configuration keys and their purpose\. You can learn more about their operation in bundle install(1) \fIbundle\-install\.1\.html\fR\.
 .
 .IP "\(bu" 4
 \fBallow_bundler_dependency_conflicts\fR (\fBBUNDLE_ALLOW_BUNDLER_DEPENDENCY_CONFLICTS\fR): Allow resolving to specifications that have dependencies on \fBbundler\fR that are incompatible with the running Bundler version\.
@@ -161,6 +178,9 @@ The following is a list of all configuration keys and their purpose\. You can le
 \fBdisable_multisource\fR (\fBBUNDLE_DISABLE_MULTISOURCE\fR): When set, Gemfiles containing multiple sources will produce errors instead of warnings\. Use \fBbundle config \-\-delete disable_multisource\fR to unset\.
 .
 .IP "\(bu" 4
+\fBdisable_platform_warnings\fR (\fBBUNDLE_DISABLE_PLATFORM_WARNINGS\fR): Disable warnings during bundle install when a dependency is unused on the current platform\.
+.
+.IP "\(bu" 4
 \fBdisable_shared_gems\fR (\fBBUNDLE_DISABLE_SHARED_GEMS\fR): Stop Bundler from accessing gems installed to RubyGems\' normal location\.
 .
 .IP "\(bu" 4
@@ -185,6 +205,9 @@ The following is a list of all configuration keys and their purpose\. You can le
 \fBglobal_gem_cache\fR (\fBBUNDLE_GLOBAL_GEM_CACHE\fR): Whether Bundler should cache all gems globally, rather than locally to the installing Ruby installation\.
 .
 .IP "\(bu" 4
+\fBglobal_path_appends_ruby_scope\fR (\fBBUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE\fR): Whether Bundler should append the Ruby scope (e\.g\. engine and ABI version) to a globally\-configured path\.
+.
+.IP "\(bu" 4
 \fBignore_messages\fR (\fBBUNDLE_IGNORE_MESSAGES\fR): When set, no post install messages will be printed\. To silence a single gem, use dot notation like \fBignore_messages\.httparty true\fR\.
 .
 .IP "\(bu" 4
@@ -215,6 +238,9 @@ The following is a list of all configuration keys and their purpose\. You can le
 \fBpath\.system\fR (\fBBUNDLE_PATH__SYSTEM\fR): Whether Bundler will install gems into the default system path (\fBGem\.dir\fR)\.
 .
 .IP "\(bu" 4
+\fBpath_relative_to_cwd\fR (\fBPATH_RELATIVE_TO_CWD\fR) Makes \fB\-\-path\fR relative to the CWD instead of the \fBGemfile\fR\.
+.
+.IP "\(bu" 4
 \fBplugins\fR (\fBBUNDLE_PLUGINS\fR): Enable Bundler\'s experimental plugin system\.
 .
 .IP "\(bu" 4
@@ -280,7 +306,7 @@ The following is a list of all configuration keys and their purpose\. You can le
 .IP "" 0
 .
 .P
-In general, you should set these settings per\-application by using the applicable flag to the [bundle install(1)][bundle\-install] or [bundle package(1)][bundle\-package] command\.
+In general, you should set these settings per\-application by using the applicable flag to the bundle install(1) \fIbundle\-install\.1\.html\fR or bundle package(1) \fIbundle\-package\.1\.html\fR command\.
 .
 .P
 You can set them globally either via environment variables or \fBbundle config\fR, whichever is preferable for your setup\. If you use both, environment variables will take preference over global settings\.
@@ -452,4 +478,20 @@ export BUNDLE_GITHUB__COM=abcd0123generatedtoken:x\-oauth\-basic
 .fi
 .
 .IP "" 0
+.
+.SH "CONFIGURE BUNDLER DIRECTORIES"
+Bundler\'s home, config, cache and plugin directories are able to be configured through environment variables\. The default location for Bundler\'s home directory is \fB~/\.bundle\fR, which all directories inherit from by default\. The following outlines the available environment variables and their default values
+.
+.IP "" 4
+.
+.nf
+
+BUNDLE_USER_HOME : $HOME/\.bundle
+BUNDLE_USER_CACHE : $BUNDLE_USER_HOME/cache
+BUNDLE_USER_CONFIG : $BUNDLE_USER_HOME/config
+BUNDLE_USER_PLUGIN : $BUNDLE_USER_HOME/plugin
+.
+.fi
+.
+.IP "" 0
 

data/man/bundle-config.1.txt

@@ -9,10 +9,20 @@ SYNOPSIS
        bundle config [name [value]]
 
 DESCRIPTION
-       This  command  allows you to interact with bundler's configuration sys-
-       tem. Bundler retrieves its configuration  from  the  local  application
-       (app/.bundle/config), environment variables, and the user's home direc-
-       tory (~/.bundle/config), in that order of priority.
+       This  command  allows you to interact with Bundler's configuration sys-
+       tem.
+
+       Bundler loads configuration settings in this order:
+
+       1.  Local config (app/.bundle/config)
+
+       2.  Environmental variables (ENV)
+
+       3.  Global config (~/.bundle/config)
+
+       4.  Bundler default config
+
+
 
        Executing bundle config with no parameters will print  a  list  of  all
        bundler configuration for the current bundle, and where that configura-
@@ -81,7 +91,7 @@ REMEMBERING OPTIONS
 	      during installation.
 
 BUILD OPTIONS
-       You  can use bundle config to give bundler the flags to pass to the gem
+       You  can use bundle config to give Bundler the flags to pass to the gem
        installer every time bundler tries to install a particular gem.
 
        A very common example, the mysql gem, requires Snow  Leopard  users  to
@@ -110,13 +120,13 @@ CONFIGURATION KEYS
        Configuration keys in bundler have two forms: the  canonical  form  and
        the environment variable form.
 
-       For  instance,  passing	the --without flag to [bundle install(1)][bun-
-       dle-install] prevents Bundler from installing certain groups  specified
-       in the Gemfile(5). Bundler persists this value in app/.bundle/config so
-       that calls to Bundler.setup do not try to find gems  from  the  Gemfile
-       that  you  didn't  install.  Additionally,  subsequent calls to [bundle
-       install(1)][bundle-install]  remember  this  setting  and  skip	 those
-       groups.
+       For  instance,  passing	the  --without	flag to bundle install(1) bun-
+       dle-install.1.html prevents  Bundler  from  installing  certain	groups
+       specified  in  the Gemfile(5). Bundler persists this value in app/.bun-
+       dle/config so that calls to Bundler.setup do not try to find gems  from
+       the  Gemfile that you didn't install. Additionally, subsequent calls to
+       bundle install(1) bundle-install.1.html remember this setting and  skip
+       those groups.
 
        The  canonical  form of this configuration is "without". To convert the
        canonical form to the environment variable  form,  capitalize  it,  and
@@ -129,8 +139,8 @@ CONFIGURATION KEYS
 
 LIST OF AVAILABLE KEYS
        The following is a list of all configuration keys  and  their  purpose.
-       You  can  learn	more about their operation in [bundle install(1)][bun-
-       dle-install].
+       You  can  learn	more  about  their operation in bundle install(1) bun-
+       dle-install.1.html.
 
        o   allow_bundler_dependency_conflicts	  (BUNDLE_ALLOW_BUNDLER_DEPEN-
 	   DENCY_CONFLICTS):  Allow  resolving	to  specifications  that  have
@@ -195,6 +205,10 @@ LIST OF AVAILABLE KEYS
 	   files containing multiple sources will produce  errors  instead  of
 	   warnings.  Use bundle config --delete disable_multisource to unset.
 
+       o   disable_platform_warnings (BUNDLE_DISABLE_PLATFORM_WARNINGS):  Dis-
+	   able  warnings during bundle install when a dependency is unused on
+	   the current platform.
+
        o   disable_shared_gems (BUNDLE_DISABLE_SHARED_GEMS): Stop Bundler from
 	   accessing gems installed to RubyGems' normal location.
 
@@ -228,41 +242,49 @@ LIST OF AVAILABLE KEYS
 	   cache all gems globally, rather than locally to the installing Ruby
 	   installation.
 
+       o   global_path_appends_ruby_scope				 (BUN-
+	   DLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE): Whether Bundler should	append
+	   the	Ruby scope (e.g. engine and ABI version) to a globally-config-
+	   ured path.
+
        o   ignore_messages (BUNDLE_IGNORE_MESSAGES): When set, no post install
 	   messages will be printed. To silence a single gem, use dot notation
 	   like ignore_messages.httparty true.
 
-       o   init_gems_rb  (BUNDLE_INIT_GEMS_RB) Generate a gems.rb instead of a
+       o   init_gems_rb (BUNDLE_INIT_GEMS_RB) Generate a gems.rb instead of  a
 	   Gemfile when running bundle init.
 
-       o   jobs (BUNDLE_JOBS): The number of gems Bundler can install in  par-
+       o   jobs  (BUNDLE_JOBS): The number of gems Bundler can install in par-
 	   allel. Defaults to 1.
 
        o   list_command (BUNDLE_LIST_COMMAND) Enable new list command feature
 
-       o   major_deprecations	(BUNDLE_MAJOR_DEPRECATIONS):  Whether  Bundler
+       o   major_deprecations  (BUNDLE_MAJOR_DEPRECATIONS):  Whether   Bundler
 	   should print deprecation warnings for behavior that will be changed
 	   in the next major version.
 
-       o   no_install  (BUNDLE_NO_INSTALL): Whether bundle package should skip
+       o   no_install (BUNDLE_NO_INSTALL): Whether bundle package should  skip
 	   installing gems.
 
-       o   no_prune (BUNDLE_NO_PRUNE): Whether Bundler should  leave  outdated
+       o   no_prune  (BUNDLE_NO_PRUNE):  Whether Bundler should leave outdated
 	   gems unpruned when caching.
 
        o   only_update_to_newer_versions     (BUNDLE_ONLY_UPDATE_TO_NEWER_VER-
 	   SIONS): During bundle update, only resolve to newer versions of the
 	   gems in the lockfile.
 
-       o   path  (BUNDLE_PATH):  The  location	on disk where all gems in your
+       o   path (BUNDLE_PATH): The location on disk where  all	gems  in  your
 	   bundle will be located regardless of $GEM_HOME or $GEM_PATH values.
-	   Bundle  gems not found in this location will be installed by bundle
-	   install. Defaults to Gem.dir. When --deployment is  used,  defaults
+	   Bundle gems not found in this location will be installed by	bundle
+	   install.  Defaults  to Gem.dir. When --deployment is used, defaults
 	   to vendor/bundle.
 
-       o   path.system	(BUNDLE_PATH__SYSTEM):	Whether  Bundler  will install
+       o   path.system (BUNDLE_PATH__SYSTEM):  Whether	Bundler  will  install
 	   gems into the default system path (Gem.dir).
 
+       o   path_relative_to_cwd  (PATH_RELATIVE_TO_CWD)  Makes --path relative
+	   to the CWD instead of the Gemfile.
+
        o   plugins (BUNDLE_PLUGINS): Enable Bundler's experimental plugin sys-
 	   tem.
 
@@ -342,8 +364,8 @@ LIST OF AVAILABLE KEYS
 
 
        In general, you should set these settings per-application by using  the
-       applicable  flag  to the [bundle install(1)][bundle-install] or [bundle
-       package(1)][bundle-package] command.
+       applicable  flag to the bundle install(1) bundle-install.1.html or bun-
+       dle package(1) bundle-package.1.html command.
 
        You can set them globally either via environment  variables  or	bundle
        config,	whichever is preferable for your setup. If you use both, envi-
@@ -485,7 +507,23 @@ CREDENTIALS FOR GEM SOURCES
 
 
 
+CONFIGURE BUNDLER DIRECTORIES
+       Bundler's  home,  config,  cache  and plugin directories are able to be
+       configured through environment  variables.  The	default  location  for
+       Bundler's  home	directory  is ~/.bundle, which all directories inherit
+       from by default. The following outlines the available environment vari-
+       ables and their default values
+
+
+
+	   BUNDLE_USER_HOME : $HOME/.bundle
+	   BUNDLE_USER_CACHE : $BUNDLE_USER_HOME/cache
+	   BUNDLE_USER_CONFIG : $BUNDLE_USER_HOME/config
+	   BUNDLE_USER_PLUGIN : $BUNDLE_USER_HOME/plugin
+
+
+
 
 
 
-				 December 2017		      BUNDLE-CONFIG(1)
+				 December 2018		      BUNDLE-CONFIG(1)

data/man/bundle-config.ronn

@@ -7,10 +7,14 @@ bundle-config(1) -- Set bundler configuration options
 
 ## DESCRIPTION
 
-This command allows you to interact with bundler's configuration system.
-Bundler retrieves its configuration from the local application (`app/.bundle/config`),
-environment variables, and the user's home directory (`~/.bundle/config`),
-in that order of priority.
+This command allows you to interact with Bundler's configuration system.
+
+Bundler loads configuration settings in this order:
+
+1. Local config (`app/.bundle/config`)
+2. Environmental variables (`ENV`)
+3. Global config (`~/.bundle/config`)
+4. Bundler default config
 
 Executing `bundle config` with no parameters will print a list of all
 bundler configuration for the current bundle, and where that configuration
@@ -76,7 +80,7 @@ The options that can be configured are:
 
 ## BUILD OPTIONS
 
-You can use `bundle config` to give bundler the flags to pass to the gem
+You can use `bundle config` to give Bundler the flags to pass to the gem
 installer every time bundler tries to install a particular gem.
 
 A very common example, the `mysql` gem, requires Snow Leopard users to
@@ -98,11 +102,11 @@ After running this command, every time bundler needs to install the
 Configuration keys in bundler have two forms: the canonical form and the
 environment variable form.
 
-For instance, passing the `--without` flag to [bundle install(1)][bundle-install]
+For instance, passing the `--without` flag to [bundle install(1)](bundle-install.1.html)
 prevents Bundler from installing certain groups specified in the Gemfile(5). Bundler
 persists this value in `app/.bundle/config` so that calls to `Bundler.setup`
 do not try to find gems from the `Gemfile` that you didn't install. Additionally,
-subsequent calls to [bundle install(1)][bundle-install] remember this setting
+subsequent calls to [bundle install(1)](bundle-install.1.html) remember this setting
 and skip those groups.
 
 The canonical form of this configuration is `"without"`. To convert the canonical
@@ -116,7 +120,7 @@ the environment variable `BUNDLE_LOCAL__RACK`.
 ## LIST OF AVAILABLE KEYS
 
 The following is a list of all configuration keys and their purpose. You can
-learn more about their operation in [bundle install(1)][bundle-install].
+learn more about their operation in [bundle install(1)](bundle-install.1.html).
 
 * `allow_bundler_dependency_conflicts` (`BUNDLE_ALLOW_BUNDLER_DEPENDENCY_CONFLICTS`):
    Allow resolving to specifications that have dependencies on `bundler` that
@@ -166,6 +170,8 @@ learn more about their operation in [bundle install(1)][bundle-install].
    When set, Gemfiles containing multiple sources will produce errors
    instead of warnings.
    Use `bundle config --delete disable_multisource` to unset.
+* `disable_platform_warnings` (`BUNDLE_DISABLE_PLATFORM_WARNINGS`):
+   Disable warnings during bundle install when a dependency is unused on the current platform.
 * `disable_shared_gems` (`BUNDLE_DISABLE_SHARED_GEMS`):
    Stop Bundler from accessing gems installed to RubyGems' normal location.
 * `disable_version_check` (`BUNDLE_DISABLE_VERSION_CHECK`):
@@ -192,6 +198,9 @@ learn more about their operation in [bundle install(1)][bundle-install].
 * `global_gem_cache` (`BUNDLE_GLOBAL_GEM_CACHE`):
    Whether Bundler should cache all gems globally, rather than locally to the
    installing Ruby installation.
+* `global_path_appends_ruby_scope` (`BUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE`):
+   Whether Bundler should append the Ruby scope (e.g. engine and ABI version)
+   to a globally-configured path.
 * `ignore_messages` (`BUNDLE_IGNORE_MESSAGES`): When set, no post install
    messages will be printed. To silence a single gem, use dot notation like
    `ignore_messages.httparty true`.
@@ -218,6 +227,8 @@ learn more about their operation in [bundle install(1)][bundle-install].
    is used, defaults to vendor/bundle.
 * `path.system` (`BUNDLE_PATH__SYSTEM`):
    Whether Bundler will install gems into the default system path (`Gem.dir`).
+* `path_relative_to_cwd` (`PATH_RELATIVE_TO_CWD`)
+   Makes `--path` relative to the CWD instead of the `Gemfile`.
 * `plugins` (`BUNDLE_PLUGINS`):
    Enable Bundler's experimental plugin system.
 * `prefer_gems_rb` (`BUNDLE_PREFER_GEMS_RB`)
@@ -277,7 +288,7 @@ learn more about their operation in [bundle install(1)][bundle-install].
    A `:`-separated list of groups whose gems bundler should not install.
 
 In general, you should set these settings per-application by using the applicable
-flag to the [bundle install(1)][bundle-install] or [bundle package(1)][bundle-package] command.
+flag to the [bundle install(1)](bundle-install.1.html) or [bundle package(1)](bundle-package.1.html) command.
 
 You can set them globally either via environment variables or `bundle config`,
 whichever is preferable for your setup. If you use both, environment variables
@@ -370,3 +381,17 @@ This is especially useful for private repositories on hosts such as Github,
 where you can use personal OAuth tokens:
 
     export BUNDLE_GITHUB__COM=abcd0123generatedtoken:x-oauth-basic
+
+
+## CONFIGURE BUNDLER DIRECTORIES
+
+Bundler's home, config, cache and plugin directories are able to be configured
+through environment variables. The default location for Bundler's home directory is
+`~/.bundle`, which all directories inherit from by default. The following
+outlines the available environment variables and their default values
+
+    BUNDLE_USER_HOME : $HOME/.bundle
+    BUNDLE_USER_CACHE : $BUNDLE_USER_HOME/cache
+    BUNDLE_USER_CONFIG : $BUNDLE_USER_HOME/config
+    BUNDLE_USER_PLUGIN : $BUNDLE_USER_HOME/plugin
+

data/man/bundle-doctor.1

@@ -0,0 +1,44 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-DOCTOR" "1" "November 2018" "" ""
+.
+.SH "NAME"
+\fBbundle\-doctor\fR \- Checks the bundle for common problems
+.
+.SH "SYNOPSIS"
+\fBbundle doctor\fR [\-\-quiet] [\-\-gemfile=GEMFILE]
+.
+.SH "DESCRIPTION"
+Checks your Gemfile and gem environment for common problems\. If issues are detected, Bundler prints them and exits status 1\. Otherwise, Bundler prints a success message and exits status 0\.
+.
+.P
+Examples of common problems caught by bundle\-doctor include:
+.
+.IP "\(bu" 4
+Invalid Bundler settings
+.
+.IP "\(bu" 4
+Mismatched Ruby versions
+.
+.IP "\(bu" 4
+Mismatched platforms
+.
+.IP "\(bu" 4
+Uninstalled gems
+.
+.IP "\(bu" 4
+Missing dependencies
+.
+.IP "" 0
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-quiet\fR
+Only output warnings and errors\.
+.
+.TP
+\fB\-\-gemfile=<gemfile>\fR
+The location of the Gemfile(5) which Bundler should use\. This defaults to a Gemfile(5) in the current working directory\. In general, Bundler will assume that the location of the Gemfile(5) is also the project\'s root and will try to find \fBGemfile\.lock\fR and \fBvendor/cache\fR relative to this location\.
+

data/man/bundle-doctor.1.txt

@@ -0,0 +1,44 @@
+BUNDLE-DOCTOR(1)					      BUNDLE-DOCTOR(1)
+
+
+
+NAME
+       bundle-doctor - Checks the bundle for common problems
+
+SYNOPSIS
+       bundle doctor [--quiet] [--gemfile=GEMFILE]
+
+DESCRIPTION
+       Checks  your Gemfile and gem environment for common problems. If issues
+       are detected, Bundler  prints  them  and  exits	status	1.  Otherwise,
+       Bundler prints a success message and exits status 0.
+
+       Examples of common problems caught by bundle-doctor include:
+
+       o   Invalid Bundler settings
+
+       o   Mismatched Ruby versions
+
+       o   Mismatched platforms
+
+       o   Uninstalled gems
+
+       o   Missing dependencies
+
+
+
+OPTIONS
+       --quiet
+	      Only output warnings and errors.
+
+       --gemfile=<gemfile>
+	      The  location  of  the Gemfile(5) which Bundler should use. This
+	      defaults to a Gemfile(5) in the current  working	directory.  In
+	      general, Bundler will assume that the location of the Gemfile(5)
+	      is also the project's root and will try to find Gemfile.lock and
+	      vendor/cache relative to this location.
+
+
+
+
+				 November 2018		      BUNDLE-DOCTOR(1)

data/man/bundle-doctor.ronn

@@ -0,0 +1,33 @@
+bundle-doctor(1) -- Checks the bundle for common problems
+=========================================================
+
+## SYNOPSIS
+
+`bundle doctor` [--quiet]
+                [--gemfile=GEMFILE]
+
+## DESCRIPTION
+
+Checks your Gemfile and gem environment for common problems. If issues
+are detected, Bundler prints them and exits status 1. Otherwise,
+Bundler prints a success message and exits status 0.
+
+Examples of common problems caught by bundle-doctor include:
+
+* Invalid Bundler settings
+* Mismatched Ruby versions
+* Mismatched platforms
+* Uninstalled gems
+* Missing dependencies
+
+## OPTIONS
+
+* `--quiet`:
+  Only output warnings and errors.
+
+* `--gemfile=<gemfile>`:
+  The location of the Gemfile(5) which Bundler should use. This defaults
+  to a Gemfile(5) in the current working directory. In general, Bundler
+  will assume that the location of the Gemfile(5) is also the project's
+  root and will try to find `Gemfile.lock` and `vendor/cache` relative
+  to this location.

data/man/bundle-exec.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-EXEC" "1" "July 2017" "" ""
+.TH "BUNDLE\-EXEC" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-exec\fR \- Execute a command in the context of the bundle
@@ -10,10 +10,10 @@
 \fBbundle exec\fR [\-\-keep\-file\-descriptors] \fIcommand\fR
 .
 .SH "DESCRIPTION"
-This command executes the command, making all gems specified in the \fBGemfile(5)\fR available to \fBrequire\fR in Ruby programs\.
+This command executes the command, making all gems specified in the [\fBGemfile(5)\fR][Gemfile(5)] available to \fBrequire\fR in Ruby programs\.
 .
 .P
-Essentially, if you would normally have run something like \fBrspec spec/my_spec\.rb\fR, and you want to use the gems specified in the \fBGemfile(5)\fR and installed via [bundle install(1)][bundle\-install], you should run \fBbundle exec rspec spec/my_spec\.rb\fR\.
+Essentially, if you would normally have run something like \fBrspec spec/my_spec\.rb\fR, and you want to use the gems specified in the [\fBGemfile(5)\fR][Gemfile(5)] and installed via bundle install(1) \fIbundle\-install\.1\.html\fR, you should run \fBbundle exec rspec spec/my_spec\.rb\fR\.
 .
 .P
 Note that \fBbundle exec\fR does not require that an executable is available on your shell\'s \fB$PATH\fR\.
@@ -25,7 +25,7 @@ Note that \fBbundle exec\fR does not require that an executable is available on
 Exec in Ruby 2\.0 began discarding non\-standard file descriptors\. When this flag is passed, exec will revert to the 1\.9 behaviour of passing all file descriptors to the new process\.
 .
 .SH "BUNDLE INSTALL \-\-BINSTUBS"
-If you use the \fB\-\-binstubs\fR flag in [bundle install(1)][bundle\-install], Bundler will automatically create a directory (which defaults to \fBapp_root/bin\fR) containing all of the executables available from gems in the bundle\.
+If you use the \fB\-\-binstubs\fR flag in bundle install(1) \fIbundle\-install\.1\.html\fR, Bundler will automatically create a directory (which defaults to \fBapp_root/bin\fR) containing all of the executables available from gems in the bundle\.
 .
 .P
 After using \fB\-\-binstubs\fR, \fBbin/rspec spec/my_spec\.rb\fR is identical to \fBbundle exec rspec spec/my_spec\.rb\fR\.

data/man/bundle-exec.1.txt

@@ -10,12 +10,12 @@ SYNOPSIS
 
 DESCRIPTION
        This  command  executes	the  command, making all gems specified in the
-       Gemfile(5) available to require in Ruby programs.
+       [Gemfile(5)][Gemfile(5)] available to require in Ruby programs.
 
        Essentially, if you  would  normally  have  run	something  like  rspec
-       spec/my_spec.rb,  and  you  want  to use the gems specified in the Gem-
-       file(5) and  installed  via  [bundle  install(1)][bundle-install],  you
-       should run bundle exec rspec spec/my_spec.rb.
+       spec/my_spec.rb,  and  you  want to use the gems specified in the [Gem-
+       file(5)][Gemfile(5)]  and  installed   via   bundle   install(1)   bun-
+       dle-install.1.html, you should run bundle exec rspec spec/my_spec.rb.
 
        Note  that bundle exec does not require that an executable is available
        on your shell's $PATH.
@@ -27,10 +27,10 @@ OPTIONS
 	      of passing all file descriptors to the new process.
 
 BUNDLE INSTALL --BINSTUBS
-       If you use the --binstubs flag in [bundle  install(1)][bundle-install],
-       Bundler	will  automatically  create  a	directory  (which  defaults to
-       app_root/bin) containing all of the executables available from gems  in
-       the bundle.
+       If  you	use  the   --binstubs	flag   in   bundle   install(1)   bun-
+       dle-install.1.html,  Bundler  will  automatically  create  a  directory
+       (which defaults to app_root/bin)  containing  all  of  the  executables
+       available from gems in the bundle.
 
        After  using --binstubs, bin/rspec spec/my_spec.rb is identical to bun-
        dle exec rspec spec/my_spec.rb.
@@ -175,4 +175,4 @@ RUBYGEMS PLUGINS
 
 
 
-				   July 2017			BUNDLE-EXEC(1)
+				 November 2018			BUNDLE-EXEC(1)

data/man/bundle-exec.ronn

@@ -8,11 +8,11 @@ bundle-exec(1) -- Execute a command in the context of the bundle
 ## DESCRIPTION
 
 This command executes the command, making all gems specified in the
-`Gemfile(5)` available to `require` in Ruby programs.
+[`Gemfile(5)`][Gemfile(5)] available to `require` in Ruby programs.
 
 Essentially, if you would normally have run something like
 `rspec spec/my_spec.rb`, and you want to use the gems specified
-in the `Gemfile(5)` and installed via [bundle install(1)][bundle-install], you
+in the [`Gemfile(5)`][Gemfile(5)] and installed via [bundle install(1)](bundle-install.1.html), you
 should run `bundle exec rspec spec/my_spec.rb`.
 
 Note that `bundle exec` does not require that an executable is
@@ -27,7 +27,7 @@ available on your shell's `$PATH`.
 
 ## BUNDLE INSTALL --BINSTUBS
 
-If you use the `--binstubs` flag in [bundle install(1)][bundle-install], Bundler will
+If you use the `--binstubs` flag in [bundle install(1)](bundle-install.1.html), Bundler will
 automatically create a directory (which defaults to `app_root/bin`)
 containing all of the executables available from gems in the bundle.
 

data/man/bundle-gem.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-GEM" "1" "December 2017" "" ""
+.TH "BUNDLE\-GEM" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-gem\fR \- Generate a project skeleton for creating a rubygem
@@ -74,7 +74,7 @@ Open the resulting GEM_NAME\.gemspec in EDITOR, or the default editor if not spe
 .SH "SEE ALSO"
 .
 .IP "\(bu" 4
-bundle\-config \fIhttp://bundler\.io/v1\.14/bundle_config\.html\fR
+bundle config(1) \fIbundle\-config\.1\.html\fR
 .
 .IP "" 0
 

data/man/bundle-gem.1.txt

@@ -81,11 +81,11 @@ OPTIONS
 	      $VISUAL, or $EDITOR.
 
 SEE ALSO
-       o   bundle-config http://bundler.io/v1.14/bundle_config.html
+       o   bundle config(1) bundle-config.1.html
 
 
 
 
 
 
-				 December 2017			 BUNDLE-GEM(1)
+				 November 2018			 BUNDLE-GEM(1)

data/man/bundle-gem.ronn

@@ -75,4 +75,4 @@ configuration file using the following names:
 
 ## SEE ALSO
 
-* [bundle-config](http://bundler.io/v1.14/bundle_config.html)
+* [bundle config(1)](bundle-config.1.html)