bundler 1.17.0.pre.1 → 1.17.0.pre.2

data/man/bundle-install.ronn

@@ -66,7 +66,7 @@ time `bundle install` is run, use `bundle config` (see bundle-config(1)).
 
 * `--force`:
   Force download every gem, even if the required versions are already available
-  locally.
+  locally. `--redownload` is an alias of this option.
 
 * `--frozen`:
   Do not allow the Gemfile.lock to be updated after this install. Exits
@@ -290,12 +290,21 @@ of a dependency of a gem in your Gemfile(5)) can result in radically
 different gems being needed to satisfy all dependencies.
 
 As a result, you `SHOULD` check your `Gemfile.lock` into version
-control. If you do not, every machine that checks out your
-repository (including your production server) will resolve all
+control, in both applications and gems. If you do not, every machine that
+checks out your repository (including your production server) will resolve all
 dependencies again, which will result in different versions of
 third-party code being used if `any` of the gems in the Gemfile(5)
 or any of their dependencies have been updated.
 
+When Bundler first shipped, the `Gemfile.lock` was included in the `.gitignore`
+file included with generated gems.  Over time, however, it became clear that
+this practice forces the pain of broken dependencies onto new contributors,
+while leaving existing contributors potentially unaware of the problem. Since
+`bundle install` is usually the first step towards a contribution, the pain of
+broken dependencies would discourage new contributors from contributing. As a
+result, we have revised our guidance for gem authors to now recommend checking
+in the lock for gems.
+
 ## CONSERVATIVE UPDATING
 
 When you make a change to the Gemfile(5) and then run `bundle install`,

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" "September 2018" "" ""
+.TH "BUNDLE\-LIST" "1" "October 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-list\fR \- List all the gems in the bundle

data/man/bundle-list.1.txt

@@ -40,4 +40,4 @@ OPTIONS
 
 
 
-				September 2018			BUNDLE-LIST(1)
+				 October 2018			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" "September 2018" "" ""
+.TH "BUNDLE\-LOCK" "1" "October 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-lock\fR \- Creates / Updates a lockfile without installing

data/man/bundle-lock.1.txt

@@ -90,4 +90,4 @@ PATCH LEVEL OPTIONS
 
 
 
-				September 2018			BUNDLE-LOCK(1)
+				 October 2018			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" "September 2018" "" ""
+.TH "BUNDLE\-OPEN" "1" "October 2018" "" ""
 .
 .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
 
 
 
-				September 2018			BUNDLE-OPEN(1)
+				 October 2018			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" "September 2018" "" ""
+.TH "BUNDLE\-OUTDATED" "1" "October 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-outdated\fR \- List installed gems with newer versions available

data/man/bundle-outdated.1.txt

@@ -128,4 +128,4 @@ FILTERING OUTPUT
 
 
 
-				September 2018		    BUNDLE-OUTDATED(1)
+				 October 2018		    BUNDLE-OUTDATED(1)

data/man/bundle-package.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PACKAGE" "1" "September 2018" "" ""
+.TH "BUNDLE\-PACKAGE" "1" "October 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application

data/man/bundle-package.1.txt

@@ -76,4 +76,4 @@ REMOTE FETCHING
 
 
 
-				September 2018		     BUNDLE-PACKAGE(1)
+				 October 2018		     BUNDLE-PACKAGE(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" "September 2018" "" ""
+.TH "BUNDLE\-PLATFORM" "1" "October 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-platform\fR \- Displays platform compatibility information

data/man/bundle-platform.1.txt

@@ -54,4 +54,4 @@ OPTIONS
 
 
 
-				September 2018		    BUNDLE-PLATFORM(1)
+				 October 2018		    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" "September 2018" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "October 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition

data/man/bundle-pristine.1.txt

@@ -41,4 +41,4 @@ DESCRIPTION
 
 
 
-				September 2018		    BUNDLE-PRISTINE(1)
+				 October 2018		    BUNDLE-PRISTINE(1)

data/man/bundle-remove.1

@@ -0,0 +1,31 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "BUNDLE\-REMOVE" "1" "October 2018" "" ""
+.
+.SH "NAME"
+\fBbundle\-remove\fR \- Removes gems from the Gemfile
+.
+.SH "SYNOPSIS"
+\fBbundle remove [GEM [GEM \.\.\.]] [\-\-install]\fR
+.
+.SH "DESCRIPTION"
+Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid\. If a gem cannot be removed, a warning is printed\. If a gem is already absent from the Gemfile, and error is raised\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-install\fR
+Runs \fBbundle install\fR after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s)\.
+.
+.P
+Example:
+.
+.P
+bundle remove rails
+.
+.P
+bundle remove rails rack
+.
+.P
+bundle remove rails rack \-\-install

data/man/bundle-remove.1.txt

@@ -0,0 +1,34 @@
+BUNDLE-REMOVE(1)					      BUNDLE-REMOVE(1)
+
+
+
+NAME
+       bundle-remove - Removes gems from the Gemfile
+
+SYNOPSIS
+       bundle remove [GEM [GEM ...]] [--install]
+
+DESCRIPTION
+       Removes the given gems from the Gemfile while ensuring that the result-
+       ing Gemfile is still valid. If a gem cannot be removed,	a  warning  is
+       printed.  If  a	gem  is  already absent from the Gemfile, and error is
+       raised.
+
+OPTIONS
+       --install
+	      Runs bundle install after the given gems have been removed  from
+	      the  Gemfile,  which  ensures  that  both  the  lockfile and the
+	      installed gems on disk are also  updated	to  remove  the  given
+	      gem(s).
+
+       Example:
+
+       bundle remove rails
+
+       bundle remove rails rack
+
+       bundle remove rails rack --install
+
+
+
+				 October 2018		      BUNDLE-REMOVE(1)

data/man/bundle-remove.ronn

@@ -0,0 +1,23 @@
+bundle-remove(1) -- Removes gems from the Gemfile
+===========================================================================
+
+## SYNOPSIS
+
+`bundle remove [GEM [GEM ...]] [--install]`
+
+## DESCRIPTION
+
+Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid. If a gem cannot be removed, a warning is printed. If a gem is already absent from the Gemfile, and error is raised.
+
+## OPTIONS
+
+* `--install`:
+  Runs `bundle install` after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s).
+
+Example:
+
+bundle remove rails
+
+bundle remove rails rack
+
+bundle remove rails rack --install

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" "September 2018" "" ""
+.TH "BUNDLE\-SHOW" "1" "October 2018" "" ""
 .
 .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
 
 
 
-				September 2018			BUNDLE-SHOW(1)
+				 October 2018			BUNDLE-SHOW(1)

data/man/bundle-update.1

@@ -1,16 +1,16 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-UPDATE" "1" "September 2018" "" ""
+.TH "BUNDLE\-UPDATE" "1" "October 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-update\fR \- Update your gems to the latest available versions
 .
 .SH "SYNOPSIS"
-\fBbundle update\fR \fI*gems\fR [\-\-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] [\-\-force] [\-\-patch|\-\-minor|\-\-major] [\-\-strict] [\-\-conservative]
 .
 .SH "DESCRIPTION"
-Update the gems specified (all gems, if none are specified), 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\.
+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\.
 .
 .P
 You would use \fBbundle update\fR to explicitly update the version of a gem\.
@@ -18,6 +18,10 @@ You would use \fBbundle update\fR to explicitly update the version of a gem\.
 .SH "OPTIONS"
 .
 .TP
+\fB\-\-all\fR
+Update all gems specified in Gemfile\.
+.
+.TP
 \fB\-\-group=<name>\fR, \fB\-g=[<name>]\fR
 Only update the gems in the specified group\. For instance, you can update all gems in the development group with \fBbundle update \-\-group development\fR\. You can also call \fBbundle update rails \-\-group test\fR to update the rails gem and all gems in the test group, for example\.
 .
@@ -55,7 +59,7 @@ Only output warnings and errors\.
 .
 .TP
 \fB\-\-force\fR
-Force downloading every gem\.
+Force downloading every gem\. \fB\-\-redownload\fR is an alias of this option\.
 .
 .TP
 \fB\-\-patch\fR
@@ -78,7 +82,7 @@ Do not allow any gem to be updated past latest \fB\-\-patch\fR | \fB\-\-minor\fR
 Use bundle install conservative update behavior and do not allow shared dependencies to be updated\.
 .
 .SH "UPDATING ALL GEMS"
-If you run \fBbundle update\fR with no parameters, bundler will ignore any previously installed gems and resolve all dependencies again based on the latest versions of all gems available in the sources\.
+If you run \fBbundle update \-\-all\fR, bundler will ignore any previously installed gems and resolve all dependencies again based on the latest versions of all gems available in the sources\.
 .
 .P
 Consider the following Gemfile(5):
@@ -149,7 +153,7 @@ After checking in the \fBGemfile\.lock\fR into version control and cloning it on
 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 Gemfile(5)\.
 .
 .P
-To do this, run \fBbundle update\fR, which will ignore the \fBGemfile\.lock\fR, 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 \fBbundle update\fR\.
+To do this, run \fBbundle update \-\-all\fR, which will ignore the \fBGemfile\.lock\fR, 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 \fBbundle update \-\-all\fR\.
 .
 .SH "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 \fBGemfile\.lock\fR\.
@@ -384,7 +388,7 @@ $ bundle update rails thin
 If you want to update all the gems to the latest possible versions that still match the gems listed in the Gemfile(5), run
 .
 .IP
-$ bundle update
+$ bundle update \-\-all
 .
 .IP "" 0
 

data/man/bundle-update.1.txt

@@ -6,12 +6,12 @@ NAME
        bundle-update - Update your gems to the latest available versions
 
 SYNOPSIS
-       bundle  update  *gems [--group=NAME] [--source=NAME] [--local] [--ruby]
-       [--bundler[=VERSION]] [--full-index] [--jobs=JOBS] [--quiet]  [--force]
-       [--patch|--minor|--major] [--strict] [--conservative]
+       bundle  update  *gems  [--all] [--group=NAME] [--source=NAME] [--local]
+       [--ruby] [--bundler[=VERSION]] [--full-index]  [--jobs=JOBS]  [--quiet]
+       [--force] [--patch|--minor|--major] [--strict] [--conservative]
 
 DESCRIPTION
-       Update  the  gems specified (all gems, if none are specified), ignoring
+       Update  the  gems specified (all gems, if --all flag is used), ignoring
        the previously installed gems specified in the  Gemfile.lock.  In  gen-
        eral, you should use bundle install(1) bundle-install.1.html to install
        the same exact gems and versions across machines.
@@ -19,6 +19,8 @@ DESCRIPTION
        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
@@ -56,7 +58,8 @@ OPTIONS
 	      Only output warnings and errors.
 
        --force
-	      Force downloading every gem.
+	      Force downloading every gem. --redownload is an  alias  of  this
+	      option.
 
        --patch
 	      Prefer updating only to next patch version.
@@ -76,9 +79,9 @@ OPTIONS
 	      shared dependencies to be updated.
 
 UPDATING ALL GEMS
-       If you run bundle update with no parameters, bundler  will  ignore  any
-       previously  installed  gems and resolve all dependencies again based on
-       the latest versions of all gems available in the sources.
+       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):
 
@@ -91,8 +94,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:
 
 
@@ -131,43 +134,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, which will ignore the Gemfile.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.
+       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.
 
 
@@ -179,7 +182,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:
 
 
@@ -197,14 +200,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
@@ -212,8 +215,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.
 
@@ -221,8 +224,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.
 
@@ -239,41 +242,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
@@ -322,26 +325,26 @@ 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
+       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
        of bar.
 
        In case 4, foo is preferred up to a minor version, but 1.5.1 won't work
-       because	the  --strict  flag removes bar 3.0.0 from consideration since
+       because the --strict flag removes bar 3.0.0  from  consideration  since
        it's a major increment.
 
-       In case 5, both foo and bar have any minor or major increments  removed
-       from  consideration  because of the --strict flag, so the most they can
+       In  case 5, both foo and bar have any minor or major increments removed
+       from consideration because of the --strict flag, so the most  they  can
        move is up to 1.4.4 and 2.0.4.
 
 RECOMMENDED WORKFLOW
-       In general, when working with an application managed with bundler,  you
+       In  general, when working with an application managed with bundler, you
        should use the following workflow:
 
        o   After you create your Gemfile(5) for the first time, run
@@ -352,7 +355,7 @@ RECOMMENDED WORKFLOW
 
 	   $ git add Gemfile.lock
 
-       o   When  checking  out this repository on another development machine,
+       o   When checking out this repository on another  development  machine,
 	   run
 
 	   $ bundle install
@@ -361,7 +364,7 @@ RECOMMENDED WORKFLOW
 
 	   $ bundle install --deployment
 
-       o   After changing the Gemfile(5) to reflect a  new  or	update	depen-
+       o   After  changing  the  Gemfile(5)  to reflect a new or update depen-
 	   dency, run
 
 	   $ bundle install
@@ -375,14 +378,14 @@ RECOMMENDED WORKFLOW
 
 	   $ bundle update rails thin
 
-       o   If you want to update all the gems to the latest possible  versions
+       o   If  you want to update all the gems to the latest possible versions
 	   that still match the gems listed in the Gemfile(5), run
 
-	   $ bundle update
+	   $ bundle update --all
 
 
 
 
 
 
-				September 2018		      BUNDLE-UPDATE(1)
+				 October 2018		      BUNDLE-UPDATE(1)