bundler 1.17.3 → 2.1.1

data/man/bundle-list.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LIST" "1" "December 2018" "" ""
+.TH "BUNDLE\-LIST" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-list\fR \- List all the gems in the bundle

data/man/bundle-list.1.txt

@@ -40,4 +40,4 @@ OPTIONS
 
 
 
-				 December 2018			BUNDLE-LIST(1)
+				 December 2019			BUNDLE-LIST(1)

data/man/bundle-lock.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LOCK" "1" "November 2018" "" ""
+.TH "BUNDLE\-LOCK" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-lock\fR \- Creates / Updates a lockfile without installing

data/man/bundle-lock.1.txt

@@ -16,16 +16,16 @@ DESCRIPTION
 OPTIONS
        --update=<*gems>
 	      Ignores  the  existing  lockfile. Resolve then updates lockfile.
-	      Taking a list of gems or updating all gems if no list is	given.
+	      Taking a list of gems or updating all gems if no list is given.
 
        --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.
 
        --print
-	      Prints the lockfile to STDOUT instead of	writing  to  the  file
+	      Prints  the  lockfile  to  STDOUT instead of writing to the file
 	      system.
 
        --lockfile=<path>
@@ -35,7 +35,7 @@ OPTIONS
 	      Fall back to using the single-file index of all gems.
 
        --add-platform
-	      Add  a  new platform to the lockfile, re-resolving for the addi-
+	      Add a new platform to the lockfile, re-resolving for  the  addi-
 	      tion of that platform.
 
        --remove-platform
@@ -51,7 +51,7 @@ OPTIONS
 	      If updating, prefer updating to next major version (default).
 
        --strict
-	      If updating, do not allow any gem  to  be  updated  past	latest
+	      If  updating,  do  not  allow  any gem to be updated past latest
 	      --patch | --minor | --major.
 
        --conservative
@@ -59,28 +59,28 @@ OPTIONS
 	      do not allow shared dependencies to be updated.
 
 UPDATING ALL GEMS
-       If you run bundle lock with  --update  option  without  list  of  gems,
-       bundler	will  ignore  any  previously  installed  gems and resolve all
-       dependencies again based on the latest versions of all  gems  available
+       If  you	run  bundle  lock  with  --update option without list of gems,
+       bundler will ignore any	previously  installed  gems  and  resolve  all
+       dependencies  again  based on the latest versions of all gems available
        in the sources.
 
 UPDATING A LIST OF GEMS
        Sometimes, you want to update a single gem in the Gemfile(5), and leave
-       the rest of the gems that you specified locked to the versions  in  the
+       the  rest  of the gems that you specified locked to the versions in the
        Gemfile.lock.
 
-       For  instance,  you  only  want	to  update  nokogiri,  run bundle lock
+       For instance, you  only	want  to  update  nokogiri,  run  bundle  lock
        --update nokogiri.
 
        Bundler will update nokogiri and any of its dependencies, but leave the
-       rest  of the gems that you specified locked to the versions in the Gem-
+       rest of the gems that you specified locked to the versions in the  Gem-
        file.lock.
 
 SUPPORTING OTHER PLATFORMS
-       If you want your bundle to support platforms other than the one	you're
+       If  you want your bundle to support platforms other than the one you're
        running locally, you can run bundle lock --add-platform PLATFORM to add
-       PLATFORM to the lockfile, force bundler to re-resolve and consider  the
-       new  platform  when picking gems, all without needing to have a machine
+       PLATFORM  to the lockfile, force bundler to re-resolve and consider the
+       new platform when picking gems, all without needing to have  a  machine
        that matches PLATFORM handy to install those platform-specific gems on.
 
        For a full explanation of gem platforms, see gem help platform.
@@ -90,4 +90,4 @@ PATCH LEVEL OPTIONS
 
 
 
-				 November 2018			BUNDLE-LOCK(1)
+				 December 2019			BUNDLE-LOCK(1)

data/man/bundle-open.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OPEN" "1" "November 2018" "" ""
+.TH "BUNDLE\-OPEN" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-open\fR \- Opens the source directory for a gem in your bundle

data/man/bundle-open.1.txt

@@ -26,4 +26,4 @@ DESCRIPTION
 
 
 
-				 November 2018			BUNDLE-OPEN(1)
+				 December 2019			BUNDLE-OPEN(1)

data/man/bundle-outdated.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OUTDATED" "1" "December 2018" "" ""
+.TH "BUNDLE\-OUTDATED" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-outdated\fR \- List installed gems with newer versions available

data/man/bundle-outdated.1.txt

@@ -128,4 +128,4 @@ FILTERING OUTPUT
 
 
 
-				 December 2018		    BUNDLE-OUTDATED(1)
+				 December 2019		    BUNDLE-OUTDATED(1)

data/man/bundle-platform.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PLATFORM" "1" "November 2018" "" ""
+.TH "BUNDLE\-PLATFORM" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-platform\fR \- Displays platform compatibility information

data/man/bundle-platform.1.txt

@@ -54,4 +54,4 @@ OPTIONS
 
 
 
-				 November 2018		    BUNDLE-PLATFORM(1)
+				 December 2019		    BUNDLE-PLATFORM(1)

data/man/bundle-pristine.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PRISTINE" "1" "November 2018" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition

data/man/bundle-pristine.1.txt

@@ -41,4 +41,4 @@ DESCRIPTION
 
 
 
-				 November 2018		    BUNDLE-PRISTINE(1)
+				 December 2019		    BUNDLE-PRISTINE(1)

data/man/bundle-remove.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-REMOVE" "1" "December 2018" "" ""
+.TH "BUNDLE\-REMOVE" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-remove\fR \- Removes gems from the Gemfile

data/man/bundle-remove.1.txt

@@ -31,4 +31,4 @@ OPTIONS
 
 
 
-				 December 2018		      BUNDLE-REMOVE(1)
+				 December 2019		      BUNDLE-REMOVE(1)

data/man/bundle-show.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-SHOW" "1" "November 2018" "" ""
+.TH "BUNDLE\-SHOW" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem

data/man/bundle-show.1.txt

@@ -24,4 +24,4 @@ OPTIONS
 
 
 
-				 November 2018			BUNDLE-SHOW(1)
+				 December 2019			BUNDLE-SHOW(1)

data/man/bundle-update.1

@@ -1,13 +1,13 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-UPDATE" "1" "December 2018" "" ""
+.TH "BUNDLE\-UPDATE" "1" "December 2019" "" ""
 .
 .SH "NAME"
 \fBbundle\-update\fR \- Update your gems to the latest available versions
 .
 .SH "SYNOPSIS"
-\fBbundle update\fR \fI*gems\fR [\-\-all] [\-\-group=NAME] [\-\-source=NAME] [\-\-local] [\-\-ruby] [\-\-bundler[=VERSION]] [\-\-full\-index] [\-\-jobs=JOBS] [\-\-quiet] [\-\-force] [\-\-patch|\-\-minor|\-\-major] [\-\-strict] [\-\-conservative]
+\fBbundle update\fR \fI*gems\fR [\-\-all] [\-\-group=NAME] [\-\-source=NAME] [\-\-local] [\-\-ruby] [\-\-bundler[=VERSION]] [\-\-full\-index] [\-\-jobs=JOBS] [\-\-quiet] [\-\-patch|\-\-minor|\-\-major] [\-\-redownload] [\-\-strict] [\-\-conservative]
 .
 .SH "DESCRIPTION"
 Update the gems specified (all gems, if \fB\-\-all\fR flag is used), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use bundle install(1) \fIbundle\-install\.1\.html\fR to install the same exact gems and versions across machines\.
@@ -58,8 +58,8 @@ Retry failed network or git requests for \fInumber\fR times\.
 Only output warnings and errors\.
 .
 .TP
-\fB\-\-force\fR
-Force downloading every gem\. \fB\-\-redownload\fR is an alias of this option\.
+\fB\-\-redownload\fR
+Force downloading every gem\.
 .
 .TP
 \fB\-\-patch\fR

data/man/bundle-update.1.txt

@@ -8,7 +8,7 @@ NAME
 SYNOPSIS
        bundle  update  *gems  [--all] [--group=NAME] [--source=NAME] [--local]
        [--ruby] [--bundler[=VERSION]] [--full-index]  [--jobs=JOBS]  [--quiet]
-       [--force] [--patch|--minor|--major] [--strict] [--conservative]
+       [--patch|--minor|--major] [--redownload] [--strict] [--conservative]
 
 DESCRIPTION
        Update  the  gems specified (all gems, if --all flag is used), ignoring
@@ -16,29 +16,29 @@ DESCRIPTION
        eral, you should use bundle install(1) bundle-install.1.html to install
        the same exact gems and versions across machines.
 
-       You would use bundle update to explicitly update the version of a  gem.
+       You would use bundle update to explicitly update the version of a gem.
 
 OPTIONS
        --all  Update all gems specified in Gemfile.
 
        --group=<name>, -g=[<name>]
-	      Only  update  the gems in the specified group. For instance, you
-	      can update all gems in the development group with bundle	update
-	      --group  development.  You  can  also  call  bundle update rails
-	      --group test to update the rails gem and all gems  in  the  test
+	      Only update the gems in the specified group. For	instance,  you
+	      can  update all gems in the development group with bundle update
+	      --group development. You	can  also  call  bundle  update  rails
+	      --group  test  to  update the rails gem and all gems in the test
 	      group, for example.
 
        --source=<name>
-	      The  name  of a :git or :path source used in the Gemfile(5). For
-	      instance,       with	 a	  :git	      source	    of
-	      http://github.com/rails/rails.git,  you would call bundle update
+	      The name of a :git or :path source used in the  Gemfile(5).  For
+	      instance,        with	   a	    :git       source	    of
+	      http://github.com/rails/rails.git, you would call bundle	update
 	      --source rails
 
        --local
-	      Do not attempt to fetch gems remotely  and  use  the  gem  cache
+	      Do  not  attempt	to  fetch  gems remotely and use the gem cache
 	      instead.
 
-       --ruby Update  the  locked  version  of	Ruby to the current version of
+       --ruby Update the locked version of Ruby  to  the  current  version  of
 	      Ruby.
 
        --bundler
@@ -57,9 +57,8 @@ OPTIONS
        --quiet
 	      Only output warnings and errors.
 
-       --force
-	      Force downloading every gem. --redownload is an  alias  of  this
-	      option.
+       --redownload
+	      Force downloading every gem.
 
        --patch
 	      Prefer updating only to next patch version.
@@ -79,8 +78,8 @@ OPTIONS
 	      shared dependencies to be updated.
 
 UPDATING ALL GEMS
-       If  you	run  bundle  update  --all, bundler will ignore any previously
-       installed gems and resolve all dependencies again based on  the	latest
+       If you run bundle update --all,	bundler  will  ignore  any  previously
+       installed  gems	and resolve all dependencies again based on the latest
        versions of all gems available in the sources.
 
        Consider the following Gemfile(5):
@@ -94,8 +93,8 @@ UPDATING ALL GEMS
 
 
 
-       When  you  run  bundle install(1) bundle-install.1.html the first time,
-       bundler will resolve all of the dependencies, all  the  way  down,  and
+       When you run bundle install(1) bundle-install.1.html  the  first  time,
+       bundler	will  resolve  all  of the dependencies, all the way down, and
        install what you need:
 
 
@@ -134,43 +133,43 @@ UPDATING ALL GEMS
 
 
 
-       As  you	can see, even though you have two gems in the Gemfile(5), your
-       application needs 26 different gems in order to run. Bundler  remembers
-       the  exact versions it installed in Gemfile.lock. The next time you run
-       bundle install(1) bundle-install.1.html, bundler skips  the  dependency
+       As you can see, even though you have two gems in the  Gemfile(5),  your
+       application  needs 26 different gems in order to run. Bundler remembers
+       the exact versions it installed in Gemfile.lock. The next time you  run
+       bundle  install(1)  bundle-install.1.html, bundler skips the dependency
        resolution and installs the same gems as it installed last time.
 
-       After  checking in the Gemfile.lock into version control and cloning it
-       on another machine,  running  bundle  install(1)  bundle-install.1.html
-       will  still  install  the  gems that you installed last time. You don't
+       After checking in the Gemfile.lock into version control and cloning  it
+       on  another  machine,  running  bundle install(1) bundle-install.1.html
+       will still install the gems that you installed  last  time.  You  don't
        need to worry that a new release of erubis or mail changes the gems you
        use.
 
-       However,  from  time to time, you might want to update the gems you are
-       using to the newest versions that still match the  gems	in  your  Gem-
+       However, from time to time, you might want to update the gems  you  are
+       using  to  the  newest  versions that still match the gems in your Gem-
        file(5).
 
-       To  do  this,  run  bundle  update  --all,  which  will ignore the Gem-
-       file.lock, and resolve all the dependencies again. Keep	in  mind  that
-       this  process  can  result  in  a significantly different set of the 25
-       gems, based on the requirements	of  new  gems  that  the  gem  authors
+       To do this, run	bundle	update	--all,	which  will  ignore  the  Gem-
+       file.lock,  and	resolve  all the dependencies again. Keep in mind that
+       this process can result in a significantly  different  set  of  the  25
+       gems,  based  on  the  requirements  of	new  gems that the gem authors
        released since the last time you ran bundle update --all.
 
 UPDATING A LIST OF GEMS
        Sometimes, you want to update a single gem in the Gemfile(5), and leave
-       the rest of the gems that you specified locked to the versions  in  the
+       the  rest  of the gems that you specified locked to the versions in the
        Gemfile.lock.
 
-       For  instance,  in  the	scenario above, imagine that nokogiri releases
+       For instance, in the scenario above,  imagine  that  nokogiri  releases
        version 1.4.4, and you want to update it without updating Rails and all
        of its dependencies. To do this, run bundle update nokogiri.
 
-       Bundler	will  update  nokogiri	and any of its dependencies, but leave
+       Bundler will update nokogiri and any of	its  dependencies,  but  leave
        alone Rails and its dependencies.
 
 OVERLAPPING DEPENDENCIES
-       Sometimes, multiple gems declared in your Gemfile(5) are  satisfied  by
-       the  same  second-level	dependency. For instance, consider the case of
+       Sometimes,  multiple  gems declared in your Gemfile(5) are satisfied by
+       the same second-level dependency. For instance, consider  the  case  of
        thin and rack-perftools-profiler.
 
 
@@ -182,7 +181,7 @@ OVERLAPPING DEPENDENCIES
 
 
 
-       The thin gem depends on	rack  >=  1.0,	while  rack-perftools-profiler
+       The  thin  gem  depends	on  rack >= 1.0, while rack-perftools-profiler
        depends on rack ~> 1.0. If you run bundle install, you get:
 
 
@@ -200,14 +199,14 @@ OVERLAPPING DEPENDENCIES
 
 
        In this case, the two gems have their own set of dependencies, but they
-       share rack in common. If you  run  bundle  update  thin,  bundler  will
-       update  daemons, eventmachine and rack, which are dependencies of thin,
-       but  not   open4   or   perftools.rb,   which   are   dependencies   of
-       rack-perftools_profiler.  Note that bundle update thin will update rack
+       share  rack  in	common.  If  you  run bundle update thin, bundler will
+       update daemons, eventmachine and rack, which are dependencies of  thin,
+       but   not   open4   or	perftools.rb,	which	are   dependencies  of
+       rack-perftools_profiler. Note that bundle update thin will update  rack
        even though it's also a dependency of rack-perftools_profiler.
 
-       In short, by default, when  you	update	a  gem	using  bundle  update,
-       bundler	will update all dependencies of that gem, including those that
+       In  short,  by  default,  when  you  update  a gem using bundle update,
+       bundler will update all dependencies of that gem, including those  that
        are also dependencies of another gem.
 
        To prevent updating shared dependencies, prior to version 1.14 the only
@@ -215,8 +214,8 @@ OVERLAPPING DEPENDENCIES
        dle-install.1.html:
 
        In this scenario, updating the thin version manually in the Gemfile(5),
-       and  then  running  bundle  install(1)  bundle-install.1.html will only
-       update daemons and eventmachine, but not rack.  For  more  information,
+       and then running  bundle  install(1)  bundle-install.1.html  will  only
+       update  daemons	and  eventmachine, but not rack. For more information,
        see  the  CONSERVATIVE  UPDATING  section  of  bundle  install(1)  bun-
        dle-install.1.html.
 
@@ -224,8 +223,8 @@ OVERLAPPING DEPENDENCIES
        vent shared dependencies from being updated.
 
 PATCH LEVEL OPTIONS
-       Version	1.14  introduced 4 patch-level options that will influence how
-       gem versions are resolved. One of the following options	can  be  used:
+       Version 1.14 introduced 4 patch-level options that will	influence  how
+       gem  versions  are  resolved. One of the following options can be used:
        --patch, --minor or --major. --strict can be added to further influence
        resolution.
 
@@ -242,41 +241,41 @@ PATCH LEVEL OPTIONS
 	      Do not allow any gem to be updated past latest --patch | --minor
 	      | --major.
 
-       When  Bundler  is  resolving  what  versions to use to satisfy declared
-       requirements in the Gemfile or in parent gems, it looks up  all	avail-
+       When Bundler is resolving what versions	to  use  to  satisfy  declared
+       requirements  in  the Gemfile or in parent gems, it looks up all avail-
        able versions, filters out any versions that don't satisfy the require-
        ment, and then, by default, sorts them from newest to oldest, consider-
        ing them in that order.
 
-       Providing  one  of  the	patch level options (e.g. --patch) changes the
-       sort order of the satisfying versions, causing Bundler to consider  the
+       Providing one of the patch level options  (e.g.	--patch)  changes  the
+       sort  order of the satisfying versions, causing Bundler to consider the
        latest --patch or --minor version available before other versions. Note
        that versions outside the stated patch level could still be resolved to
        if necessary to find a suitable dependency graph.
 
-       For  example,  if gem 'foo' is locked at 1.0.2, with no gem requirement
-       defined in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1,  2.0.0
+       For example, if gem 'foo' is locked at 1.0.2, with no  gem  requirement
+       defined	in the Gemfile, and versions 1.0.3, 1.0.4, 1.1.0, 1.1.1, 2.0.0
        all exist, the default order of preference by default (--major) will be
        "2.0.0, 1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2".
 
-       If the --patch option is used, the order of preference will  change  to
+       If  the	--patch option is used, the order of preference will change to
        "1.0.4, 1.0.3, 1.0.2, 1.1.1, 1.1.0, 2.0.0".
 
-       If  the	--minor option is used, the order of preference will change to
+       If the --minor option is used, the order of preference will  change  to
        "1.1.1, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 2.0.0".
 
-       Combining the --strict option with any of the patch level options  will
-       remove  any  versions  beyond  the  scope of the patch level option, to
+       Combining  the --strict option with any of the patch level options will
+       remove any versions beyond the scope of	the  patch  level  option,  to
        ensure that no gem is updated that far.
 
-       To continue the previous example, if both --patch and --strict  options
+       To  continue the previous example, if both --patch and --strict options
        are used, the available versions for resolution would be "1.0.4, 1.0.3,
-       1.0.2". If --minor and --strict are used, it would  be  "1.1.1,	1.1.0,
+       1.0.2".	If  --minor  and --strict are used, it would be "1.1.1, 1.1.0,
        1.0.4, 1.0.3, 1.0.2".
 
-       Gem  requirements  as  defined  in  the Gemfile will still be the first
+       Gem requirements as defined in the Gemfile  will  still	be  the  first
        determining factor for what versions are available. If the gem require-
-       ment  for foo in the Gemfile is '~> 1.0', that will accomplish the same
+       ment for foo in the Gemfile is '~> 1.0', that will accomplish the  same
        thing as providing the --minor and --strict options.
 
 PATCH LEVEL EXAMPLES
@@ -325,11 +324,11 @@ PATCH LEVEL EXAMPLES
 
 
 
-       In case 1, bar is upgraded to 2.1.1, a minor version increase,  because
+       In  case 1, bar is upgraded to 2.1.1, a minor version increase, because
        the dependency from foo 1.4.5 required it.
 
-       In  case  2,  only  foo	is  requested  to be unlocked, but bar is also
-       allowed to move because it's not a declared dependency in the  Gemfile.
+       In case 2, only foo is requested  to  be  unlocked,  but  bar  is  also
+       allowed to move because it's not a declared dependency in the Gemfile.
 
        In  case 3, bar goes up a whole major release, because a minor increase
        is preferred now for foo, and when it goes to 1.5.1, it requires  3.0.0
@@ -388,4 +387,4 @@ RECOMMENDED WORKFLOW
 
 
 
-				 December 2018		      BUNDLE-UPDATE(1)
+				 December 2019		      BUNDLE-UPDATE(1)