bundler 2.0.0.pre.1 → 2.1.0.pre.3

data/man/bundle-doctor.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-DOCTOR" "1" "October 2018" "" ""
+.TH "BUNDLE\-DOCTOR" "1" "November 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-doctor\fR \- Checks the bundle for common problems

data/man/bundle-doctor.1.txt

@@ -41,4 +41,4 @@ OPTIONS
 
 
 
-				 October 2018		      BUNDLE-DOCTOR(1)
+				 November 2019		      BUNDLE-DOCTOR(1)

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" "October 2018" "" ""
+.TH "BUNDLE\-EXEC" "1" "November 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-exec\fR \- Execute a command in the context of the bundle
@@ -155,7 +155,7 @@ You can find a list of all the gems containing gem plugins by running
 .
 .nf
 
-ruby \-rubygems \-e "puts Gem\.find_files(\'rubygems_plugin\.rb\')"
+ruby \-rrubygems \-e "puts Gem\.find_files(\'rubygems_plugin\.rb\')"
 .
 .fi
 .

data/man/bundle-exec.1.txt

@@ -165,7 +165,7 @@ RUBYGEMS PLUGINS
 
 
 
-	   ruby -rubygems -e "puts Gem.find_files('rubygems_plugin.rb')"
+	   ruby -rrubygems -e "puts Gem.find_files('rubygems_plugin.rb')"
 
 
 
@@ -175,4 +175,4 @@ RUBYGEMS PLUGINS
 
 
 
-				 October 2018			BUNDLE-EXEC(1)
+				 November 2019			BUNDLE-EXEC(1)

data/man/bundle-exec.ronn

@@ -145,7 +145,7 @@ their plugins.
 You can find a list of all the gems containing gem plugins
 by running
 
-    ruby -rubygems -e "puts Gem.find_files('rubygems_plugin.rb')"
+    ruby -rrubygems -e "puts Gem.find_files('rubygems_plugin.rb')"
 
 At the very least, you should remove all but the newest
 version of each gem plugin, and also remove all gem plugins

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" "October 2018" "" ""
+.TH "BUNDLE\-GEM" "1" "November 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-gem\fR \- Generate a project skeleton for creating a rubygem

data/man/bundle-gem.1.txt

@@ -77,8 +77,8 @@ OPTIONS
 
        -e, --edit[=EDITOR]
 	      Open the resulting GEM_NAME.gemspec in EDITOR,  or  the  default
-	      editor   if  not	specified.  The  default  is  $BUNDLER_EDITOR,
-	      $VISUAL, or $EDITOR.
+	      editor  if  not specified. The default is $BUNDLER_EDITOR, $VIS-
+	      UAL, or $EDITOR.
 
 SEE ALSO
        o   bundle config(1) bundle-config.1.html
@@ -88,4 +88,4 @@ SEE ALSO
 
 
 
-				 October 2018			 BUNDLE-GEM(1)
+				 November 2019			 BUNDLE-GEM(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" "October 2018" "" ""
+.TH "BUNDLE\-INFO" "1" "November 2019" "" ""
 .
 .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
 
 
 
-				 October 2018			BUNDLE-INFO(1)
+				 November 2019			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" "October 2018" "" ""
+.TH "BUNDLE\-INIT" "1" "November 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-init\fR \- Generates a Gemfile into the current working directory
@@ -22,4 +22,4 @@ Use the specified \.gemspec to create the [\fBGemfile(5)\fR][Gemfile(5)]
 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
+Gemfile(5) \fIhttps://bundler\.io/man/gemfile\.5\.html\fR

data/man/bundle-init.1.txt

@@ -27,8 +27,8 @@ FILES
        string literals in the file being implicitly frozen.
 
 SEE ALSO
-       Gemfile(5) http://bundler.io/man/gemfile.5.html
+       Gemfile(5) https://bundler.io/man/gemfile.5.html
 
 
 
-				 October 2018			BUNDLE-INIT(1)
+				 November 2019			BUNDLE-INIT(1)

data/man/bundle-init.ronn

@@ -26,4 +26,4 @@ results in all string literals in the file being implicitly frozen.
 
 ## SEE ALSO
 
-[Gemfile(5)](http://bundler.io/man/gemfile.5.html)
+[Gemfile(5)](https://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" "October 2018" "" ""
+.TH "BUNDLE\-INJECT" "1" "November 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile

data/man/bundle-inject.1.txt

@@ -29,4 +29,4 @@ DESCRIPTION
 
 
 
-				 October 2018		      BUNDLE-INJECT(1)
+				 November 2019		      BUNDLE-INJECT(1)

data/man/bundle-install.1

@@ -1,13 +1,13 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INSTALL" "1" "November 2018" "" ""
+.TH "BUNDLE\-INSTALL" "1" "November 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-install\fR \- Install the dependencies specified in your Gemfile
 .
 .SH "SYNOPSIS"
-\fBbundle install\fR [\-\-binstubs[=DIRECTORY]] [\-\-clean] [\-\-deployment] [\-\-force] [\-\-frozen] [\-\-full\-index] [\-\-gemfile=GEMFILE] [\-\-jobs=NUMBER] [\-\-local] [\-\-no\-cache] [\-\-no\-prune] [\-\-path PATH] [\-\-quiet] [\-\-retry=NUMBER] [\-\-shebang] [\-\-standalone[=GROUP[ GROUP\.\.\.]]] [\-\-system] [\-\-trust\-policy=POLICY] [\-\-with=GROUP[ GROUP\.\.\.]] [\-\-without=GROUP[ GROUP\.\.\.]]
+\fBbundle install\fR [\-\-binstubs[=DIRECTORY]] [\-\-clean] [\-\-deployment] [\-\-frozen] [\-\-full\-index] [\-\-gemfile=GEMFILE] [\-\-jobs=NUMBER] [\-\-local] [\-\-no\-cache] [\-\-no\-prune] [\-\-path PATH] [\-\-quiet] [\-\-redownload] [\-\-retry=NUMBER] [\-\-shebang] [\-\-standalone[=GROUP[ GROUP\.\.\.]]] [\-\-system] [\-\-trust\-policy=POLICY] [\-\-with=GROUP[ GROUP\.\.\.]] [\-\-without=GROUP[ GROUP\.\.\.]]
 .
 .SH "DESCRIPTION"
 Install the gems specified in your Gemfile(5)\. If this is the first time you run bundle install (and a \fBGemfile\.lock\fR does not exist), Bundler will fetch all remote sources, resolve dependencies and install all needed gems\.
@@ -23,7 +23,10 @@ To apply any of \fB\-\-binstubs\fR, \fB\-\-deployment\fR, \fB\-\-path\fR, or \fB
 .
 .TP
 \fB\-\-binstubs[=<directory>]\fR
-Creates a directory (defaults to \fB~/bin\fR) and place any executables from the gem there\. These executables run in Bundler\'s context\. If used, you might add this directory to your environment\'s \fBPATH\fR variable\. For instance, if the \fBrails\fR gem comes with a \fBrails\fR executable, this flag will create a \fBbin/rails\fR executable that ensures that all referred dependencies will be resolved using the bundled gems\.
+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 \fBbin/\fR\. This lets you link the binstub inside of an application to the exact gem version the application needs\.
+.
+.IP
+Creates a directory (defaults to \fB~/bin\fR) 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 \fBPATH\fR variable\. For instance, if the \fBrails\fR gem comes with a \fBrails\fR executable, this flag will create a \fBbin/rails\fR executable that ensures that all referred dependencies will be resolved using the bundled gems\.
 .
 .TP
 \fB\-\-clean\fR
@@ -34,8 +37,8 @@ On finishing the installation Bundler is going to remove any gems not present in
 In \fIdeployment mode\fR, Bundler will \'roll\-out\' the bundle for production or CI use\. Please check carefully if you want to have this option enabled in your development environment\.
 .
 .TP
-\fB\-\-force\fR
-Force download every gem, even if the required versions are already available locally\. \fB\-\-redownload\fR is an alias of this option\.
+\fB\-\-redownload\fR
+Force download every gem, even if the required versions are already available locally\.
 .
 .TP
 \fB\-\-frozen\fR

data/man/bundle-install.1.txt

@@ -7,8 +7,8 @@ NAME
 
 SYNOPSIS
        bundle	install   [--binstubs[=DIRECTORY]]   [--clean]	[--deployment]
-       [--force] [--frozen] [--full-index] [--gemfile=GEMFILE] [--jobs=NUMBER]
-       [--local]    [--no-cache]    [--no-prune]   [--path   PATH]   [--quiet]
+       [--frozen] [--full-index] [--gemfile=GEMFILE] [--jobs=NUMBER] [--local]
+       [--no-cache]   [--no-prune]   [--path  PATH]  [--quiet]	[--redownload]
        [--retry=NUMBER] [--shebang] [--standalone[=GROUP[ GROUP...]]]  [--sys-
        tem]   [--trust-policy=POLICY]	[--with=GROUP[	 GROUP...]]   [--with-
        out=GROUP[ GROUP...]]
@@ -34,7 +34,13 @@ OPTIONS
        time bundle install is run, use bundle config (see bundle-config(1)).
 
        --binstubs[=<directory>]
-	      Creates a directory (defaults to ~/bin) and place  any  executa-
+	      Binstubs are scripts that wrap around executables. Bundler  cre-
+	      ates  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 applica-
+	      tion needs.
+
+	      Creates a directory (defaults to ~/bin) and places any  executa-
 	      bles from the gem there. These executables run in Bundler's con-
 	      text. If used, you might add this  directory  to	your  environ-
 	      ment's  PATH variable. For instance, if the rails gem comes with
@@ -52,58 +58,57 @@ OPTIONS
 	      duction  or  CI  use. Please check carefully if you want to have
 	      this option enabled in your development environment.
 
-       --force
+       --redownload
 	      Force download every gem, even  if  the  required  versions  are
-	      already  available  locally.  --redownload  is  an alias of this
-	      option.
+	      already available locally.
 
        --frozen
-	      Do not allow the Gemfile.lock to be updated after this  install.
-	      Exits  non-zero  if  there  are  going to be changes to the Gem-
+	      Do  not allow the Gemfile.lock to be updated after this install.
+	      Exits non-zero if there are going to  be	changes  to  the  Gem-
 	      file.lock.
 
        --full-index
 	      Bundler will not call Rubygems' API endpoint (default) but down-
 	      load and cache a (currently big) index file of all gems. Perfor-
-	      mance can be improved for large bundles that  seldom  change  by
+	      mance  can  be  improved for large bundles that seldom change by
 	      enabling this option.
 
        --gemfile=<gemfile>
-	      The  location  of  the Gemfile(5) which Bundler should use. This
-	      defaults to a Gemfile(5) in the current  working	directory.  In
+	      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.
 
        --jobs=[<number>], -j[<number>]
-	      The  maximum  number  of parallel download and install jobs. The
+	      The maximum number of parallel download and  install  jobs.  The
 	      default is 1.
 
        --local
 	      Do not attempt to connect to rubygems.org. Instead, Bundler will
-	      use  the	gems  already  present	in  Rubygems' cache or in ven-
-	      dor/cache. Note that  if	a  appropriate	platform-specific  gem
+	      use the gems already present  in	Rubygems'  cache  or  in  ven-
+	      dor/cache.  Note	that  if  a  appropriate platform-specific gem
 	      exists on rubygems.org it will not be found.
 
        --no-cache
-	      Do  not  update the cache in vendor/cache with the newly bundled
-	      gems. This does not remove any gems in the cache but  keeps  the
+	      Do not update the cache in vendor/cache with the	newly  bundled
+	      gems.  This  does not remove any gems in the cache but keeps the
 	      newly bundled gems from being cached during the install.
 
        --no-prune
-	      Don't  remove  stale  gems  from the cache when the installation
+	      Don't remove stale gems from the	cache  when  the  installation
 	      finishes.
 
        --path=<path>
-	      The location to install the specified gems to. This defaults  to
-	      Rubygems'  setting.  Bundler shares this location with Rubygems,
-	      gem install ... will have gem installed there,  too.  Therefore,
-	      gems  installed  without	a  --path  ... setting will show up by
+	      The  location to install the specified gems to. This defaults to
+	      Rubygems' setting. Bundler shares this location  with  Rubygems,
+	      gem  install  ... will have gem installed there, too. Therefore,
+	      gems installed without a --path ...  setting  will  show	up  by
 	      calling gem list. Accordingly, gems installed to other locations
 	      will not get listed.
 
        --quiet
-	      Do  not  print  progress	information  to  the  standard output.
+	      Do not  print  progress  information  to	the  standard  output.
 	      Instead, Bundler will exit using a status code ($?).
 
        --retry=[<number>]
@@ -111,34 +116,34 @@ OPTIONS
 
        --shebang=<ruby-executable>
 	      Uses the specified ruby executable (usually ruby) to execute the
-	      scripts  created with --binstubs. In addition, if you use --bin-
-	      stubs together with --shebang jruby these  executables  will  be
+	      scripts created with --binstubs. In addition, if you use	--bin-
+	      stubs  together  with  --shebang jruby these executables will be
 	      changed to execute jruby instead.
 
        --standalone[=<list>]
-	      Makes  a	bundle	that can work without depending on Rubygems or
-	      Bundler at runtime. A space separated list of groups to  install
-	      has  to  be  specified. Bundler creates a directory named bundle
+	      Makes a bundle that can work without depending  on  Rubygems  or
+	      Bundler  at runtime. A space separated list of groups to install
+	      has to be specified. Bundler creates a  directory  named	bundle
 	      and  installs  the  bundle  there.  It  also  generates  a  bun-
-	      dle/bundler/setup.rb  file to replace Bundler's own setup in the
-	      manner required. Using this option implicitly sets  path,  which
+	      dle/bundler/setup.rb file to replace Bundler's own setup in  the
+	      manner  required.  Using this option implicitly sets path, which
 	      is a [remembered option][REMEMBERED OPTIONS].
 
        --system
-	      Installs	the  gems  specified  in  the  bundle  to the system's
-	      Rubygems location. This overrides any previous configuration  of
+	      Installs the gems  specified  in	the  bundle  to  the  system's
+	      Rubygems	location. This overrides any previous configuration of
 	      --path.
 
        --trust-policy=[<policy>]
-	      Apply  the  Rubygems security policy policy, where policy is one
-	      of HighSecurity, MediumSecurity, LowSecurity,  AlmostNoSecurity,
+	      Apply the Rubygems security policy policy, where policy  is  one
+	      of  HighSecurity, MediumSecurity, LowSecurity, AlmostNoSecurity,
 	      or NoSecurity. For more details, please see the Rubygems signing
 	      documentation linked below in SEE ALSO.
 
        --with=<list>
 	      A space-separated list of groups referencing gems to install. If
-	      an  optional group is given it is installed. If a group is given
-	      that is in the remembered list of groups given to --without,  it
+	      an optional group is given it is installed. If a group is  given
+	      that  is in the remembered list of groups given to --without, it
 	      is removed from that list.
 
        --without=<list>
@@ -148,47 +153,47 @@ OPTIONS
 
 DEPLOYMENT MODE
        Bundler's defaults are optimized for development. To switch to defaults
-       optimized for deployment and for CI, use the --deployment flag. Do  not
-       activate  deployment  mode on development machines, as it will cause an
+       optimized  for deployment and for CI, use the --deployment flag. Do not
+       activate deployment mode on development machines, as it will  cause  an
        error when the Gemfile(5) is modified.
 
        1.  A Gemfile.lock is required.
 
 	   To ensure that the same versions of the gems you developed with and
-	   tested  with  are  also  used  in  deployments,  a  Gemfile.lock is
+	   tested with	are  also  used  in  deployments,  a  Gemfile.lock  is
 	   required.
 
-	   This is mainly to ensure that  you  remember  to  check  your  Gem-
+	   This  is  mainly  to  ensure  that  you remember to check your Gem-
 	   file.lock into version control.
 
        2.  The Gemfile.lock must be up to date
 
-	   In  development,  you  can modify your Gemfile(5) and re-run bundle
+	   In development, you can modify your Gemfile(5)  and	re-run	bundle
 	   install to conservatively update your Gemfile.lock snapshot.
 
-	   In deployment, your Gemfile.lock should be up-to-date with  changes
+	   In  deployment, your Gemfile.lock should be up-to-date with changes
 	   made in your Gemfile(5).
 
-       3.  Gems  are  installed to vendor/bundle not your default system loca-
+       3.  Gems are installed to vendor/bundle not your default  system  loca-
 	   tion
 
-	   In development, it's convenient to share  the  gems	used  in  your
-	   application	with  other applications and other scripts that run on
+	   In  development,  it's  convenient  to  share the gems used in your
+	   application with other applications and other scripts that  run  on
 	   the system.
 
-	   In deployment, isolation is a more important default. In  addition,
-	   the	user  deploying  the  application  may	not have permission to
-	   install gems to the system, or the web server may not have  permis-
+	   In  deployment, isolation is a more important default. In addition,
+	   the user deploying the  application	may  not  have	permission  to
+	   install  gems to the system, or the web server may not have permis-
 	   sion to read them.
 
-	   As  a result, bundle install --deployment installs gems to the ven-
-	   dor/bundle directory in the application.  This  may	be  overridden
+	   As a result, bundle install --deployment installs gems to the  ven-
+	   dor/bundle  directory  in  the  application. This may be overridden
 	   using the --path option.
 
 
 
 SUDO USAGE
-       By  default, Bundler installs gems to the same location as gem install.
+       By default, Bundler installs gems to the same location as gem install.
 
        In some cases, that location may not be writable by your Unix user.  In
        that case, Bundler will stage everything in a temporary directory, then
@@ -393,4 +398,4 @@ SEE ALSO
 
 
 
-				 November 2018		     BUNDLE-INSTALL(1)
+				 November 2019		     BUNDLE-INSTALL(1)

data/man/bundle-install.ronn

@@ -6,7 +6,6 @@ bundle-install(1) -- Install the dependencies specified in your Gemfile
 `bundle install` [--binstubs[=DIRECTORY]]
                  [--clean]
                  [--deployment]
-                 [--force]
                  [--frozen]
                  [--full-index]
                  [--gemfile=GEMFILE]
@@ -16,6 +15,7 @@ bundle-install(1) -- Install the dependencies specified in your Gemfile
                  [--no-prune]
                  [--path PATH]
                  [--quiet]
+                 [--redownload]
                  [--retry=NUMBER]
                  [--shebang]
                  [--standalone[=GROUP[ GROUP...]]]
@@ -47,7 +47,12 @@ To apply any of `--binstubs`, `--deployment`, `--path`, or `--without` every
 time `bundle install` is run, use `bundle config` (see bundle-config(1)).
 
 * `--binstubs[=<directory>]`:
-  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
@@ -64,9 +69,9 @@ time `bundle install` is run, use `bundle config` (see bundle-config(1)).
   production or CI use. Please check carefully if you want to have this option
   enabled in your development environment.
 
-* `--force`:
+* `--redownload`:
   Force download every gem, even if the required versions are already available
-  locally. `--redownload` is an alias of this option.
+  locally.
 
 * `--frozen`:
   Do not allow the Gemfile.lock to be updated after this install. Exits