bundler 1.16.1 → 1.16.2

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)]
 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)] 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)].
 
 * `allow_bundler_dependency_conflicts` (`BUNDLE_ALLOW_BUNDLER_DEPENDENCY_CONFLICTS`):
    Allow resolving to specifications that have dependencies on `bundler` that
@@ -277,7 +281,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)] or [bundle package(1)][bundle-package(1)] 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

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" "March 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.
+
+
+
+
+				  March 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" "February 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)][bundle\-install(1)], 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)][bundle\-install(1)], 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)], 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)],  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)
+				 February 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)], 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)], 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" "February 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)][bundle\-config(1)]
 .
 .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)]
 
 
 
 
 
 
-				 December 2017			 BUNDLE-GEM(1)
+				 February 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)]

data/man/bundle-info.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INFO" "1" "February 2017" "" ""
+.TH "BUNDLE\-INFO" "1" "January 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-info\fR \- Show information for the given gem in your bundle

data/man/bundle-info.1.txt

@@ -18,4 +18,4 @@ OPTIONS
 
 
 
-				 February 2017			BUNDLE-INFO(1)
+				 January 2018			BUNDLE-INFO(1)

data/man/bundle-init.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INIT" "1" "February 2017" "" ""
+.TH "BUNDLE\-INIT" "1" "May 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-init\fR \- Generates a Gemfile into the current working directory
@@ -10,11 +10,16 @@
 \fBbundle init\fR [\-\-gemspec=FILE]
 .
 .SH "DESCRIPTION"
-Init generates a default \fBGemfile(5)\fR in the current working directory\. When adding a \fBGemfile(5)\fR to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created \fBGemfile(5)\fR\.
+Init generates a default [\fBGemfile(5)\fR][Gemfile(5)] in the current working directory\. When adding a [\fBGemfile(5)\fR][Gemfile(5)] to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created [\fBGemfile(5)\fR][Gemfile(5)]\.
 .
 .SH "OPTIONS"
 .
 .TP
 \fB\-\-gemspec\fR
-Use the specified \.gemspec to create the \fBGemfile(5)\fR
-
+Use the specified \.gemspec to create the [\fBGemfile(5)\fR][Gemfile(5)]
+.
+.SH "FILES"
+Included in the default [\fBGemfile(5)\fR][Gemfile(5)] generated is the line \fB# frozen_string_literal: true\fR\. This is a magic comment supported for the first time in Ruby 2\.3\. The presence of this line results in all string literals in the file being implicitly frozen\.
+.
+.SH "SEE ALSO"
+Gemfile(5) \fIhttp://bundler\.io/man/gemfile\.5\.html\fR

data/man/bundle-init.1.txt

@@ -9,16 +9,26 @@ SYNOPSIS
        bundle init [--gemspec=FILE]
 
 DESCRIPTION
-       Init  generates	a default Gemfile(5) in the current working directory.
-       When adding a Gemfile(5) to a gem with a gemspec, the --gemspec	option
-       will  automatically  add  each dependency listed in the gemspec file to
-       the newly created Gemfile(5).
+       Init  generates a default [Gemfile(5)][Gemfile(5)] in the current work-
+       ing directory. When adding a [Gemfile(5)][Gemfile(5)] to a gem  with  a
+       gemspec,  the  --gemspec  option will automatically add each dependency
+       listed in the gemspec  file  to	the  newly  created  [Gemfile(5)][Gem-
+       file(5)].
 
 OPTIONS
        --gemspec
-	      Use the specified .gemspec to create the Gemfile(5)
+	      Use  the	specified  .gemspec  to  create  the [Gemfile(5)][Gem-
+	      file(5)]
 
+FILES
+       Included in the default [Gemfile(5)][Gemfile(5)] generated is the  line
+       #  frozen_string_literal:  true.  This is a magic comment supported for
+       the first time in Ruby 2.3. The presence of this line  results  in  all
+       string literals in the file being implicitly frozen.
 
+SEE ALSO
+       Gemfile(5) http://bundler.io/man/gemfile.5.html
 
 
-				 February 2017			BUNDLE-INIT(1)
+
+				   May 2018			BUNDLE-INIT(1)

data/man/bundle-init.ronn

@@ -7,12 +7,23 @@ bundle-init(1) -- Generates a Gemfile into the current working directory
 
 ## DESCRIPTION
 
-Init generates a default `Gemfile(5)` in the current working directory. When
-adding a `Gemfile(5)` to a gem with a gemspec, the `--gemspec` option will
+Init generates a default [`Gemfile(5)`][Gemfile(5)] in the current working directory. When
+adding a [`Gemfile(5)`][Gemfile(5)] to a gem with a gemspec, the `--gemspec` option will
 automatically add each dependency listed in the gemspec file to the newly
-created `Gemfile(5)`.
+created [`Gemfile(5)`][Gemfile(5)].
 
 ## OPTIONS
 
 * `--gemspec`:
-  Use the specified .gemspec to create the `Gemfile(5)`
+  Use the specified .gemspec to create the [`Gemfile(5)`][Gemfile(5)]
+
+## FILES
+
+Included in the default [`Gemfile(5)`][Gemfile(5)]
+generated is the line `# frozen_string_literal: true`. This is a magic comment
+supported for the first time in Ruby 2.3. The presence of this line
+results in all string literals in the file being implicitly frozen.
+
+## SEE ALSO
+
+[Gemfile(5)](http://bundler.io/man/gemfile.5.html)

data/man/bundle-inject.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INJECT" "1" "February 2017" "" ""
+.TH "BUNDLE\-INJECT" "1" "February 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile
@@ -10,10 +10,10 @@
 \fBbundle inject\fR [GEM] [VERSION]
 .
 .SH "DESCRIPTION"
-Adds the named gem(s) with their version requirements to the resolved \fBGemfile(5)\fR\.
+Adds the named gem(s) with their version requirements to the resolved [\fBGemfile(5)\fR][Gemfile(5)]\.
 .
 .P
-This command will add the gem to both your \fBGemfile(5)\fR and Gemfile\.lock if it isn\'t listed yet\.
+This command will add the gem to both your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock if it isn\'t listed yet\.
 .
 .P
 Example:
@@ -30,4 +30,4 @@ bundle inject \'rack\' \'> 0\'
 .IP "" 0
 .
 .P
-This will inject the \'rack\' gem with a version greater than 0 in your \fBGemfile(5)\fR and Gemfile\.lock
+This will inject the \'rack\' gem with a version greater than 0 in your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock