bundler 1.16.1 → 1.17.3

data/man/bundle-open.1.txt

@@ -26,4 +26,4 @@ DESCRIPTION
 
 
 
-				 February 2017			BUNDLE-OPEN(1)
+				 November 2018			BUNDLE-OPEN(1)

data/man/bundle-outdated.1

@@ -1,13 +1,13 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OUTDATED" "1" "July 2017" "" ""
+.TH "BUNDLE\-OUTDATED" "1" "December 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-outdated\fR \- List installed gems with newer versions available
 .
 .SH "SYNOPSIS"
-\fBbundle outdated\fR [GEM] [\-\-local] [\-\-pre] [\-\-source] [\-\-strict] [\-\-parseable | \-\-porcelain] [\-\-group=GROUP] [\-\-groups] [\-\-update\-strict] [\-\-patch|\-\-minor|\-\-major] [\-\-filter\-major] [\-\-filter\-minor] [\-\-filter\-patch]
+\fBbundle outdated\fR [GEM] [\-\-local] [\-\-pre] [\-\-source] [\-\-strict] [\-\-parseable | \-\-porcelain] [\-\-group=GROUP] [\-\-groups] [\-\-update\-strict] [\-\-patch|\-\-minor|\-\-major] [\-\-filter\-major] [\-\-filter\-minor] [\-\-filter\-patch] [\-\-only\-explicit]
 .
 .SH "DESCRIPTION"
 Outdated lists the names and versions of gems that have a newer version available in the given source\. Calling outdated with [GEM [GEM]] will only check for newer versions of the given gems\. Prerelease gems are ignored by default\. If your gems are up to date, Bundler will exit with a status of 0\. Otherwise, it will exit 1\.
@@ -70,8 +70,12 @@ Only list minor newer versions\.
 \fB\-\-filter\-patch\fR
 Only list patch newer versions\.
 .
+.TP
+\fB\-\-only\-explicit\fR
+Only list gems specified in your Gemfile, not their dependencies\.
+.
 .SH "PATCH LEVEL OPTIONS"
-See [bundle update(1)][bundle\-update] for details\.
+See bundle update(1) \fIbundle\-update\.1\.html\fR for details\.
 .
 .P
 One difference between the patch level options in \fBbundle update\fR and here is the \fB\-\-strict\fR option\. \fB\-\-strict\fR was already an option on outdated before the patch level options were added\. \fB\-\-strict\fR wasn\'t altered, and the \fB\-\-update\-strict\fR option on \fBoutdated\fR reflects what \fB\-\-strict\fR does on \fBbundle update\fR\.

data/man/bundle-outdated.1.txt

@@ -9,7 +9,7 @@ SYNOPSIS
        bundle	outdated   [GEM]   [--local]   [--pre]	[--source]  [--strict]
        [--parseable	|     --porcelain]     [--group=GROUP]	    [--groups]
        [--update-strict]  [--patch|--minor|--major]  [--filter-major]  [--fil-
-       ter-minor] [--filter-patch]
+       ter-minor] [--filter-patch] [--only-explicit]
 
 DESCRIPTION
        Outdated lists the names and versions of gems that have a newer version
@@ -62,17 +62,21 @@ OPTIONS
        --filter-patch
 	      Only list patch newer versions.
 
+       --only-explicit
+	      Only list gems specified in your Gemfile,  not  their  dependen-
+	      cies.
+
 PATCH LEVEL OPTIONS
-       See [bundle update(1)][bundle-update] for details.
+       See bundle update(1) bundle-update.1.html for details.
 
-       One difference between the patch level options  in  bundle  update  and
+       One  difference	between  the  patch level options in bundle update and
        here is the --strict option. --strict was already an option on outdated
        before the patch level options were added. --strict wasn't altered, and
-       the  --update-strict  option on outdated reflects what --strict does on
+       the --update-strict option on outdated reflects what --strict  does  on
        bundle update.
 
 FILTERING OUTPUT
-       The 3 filtering options do  not	affect	the  resolution  of  versions,
+       The  3  filtering  options  do  not  affect the resolution of versions,
        merely what versions are shown in the output.
 
        If the regular output shows the following:
@@ -119,9 +123,9 @@ FILTERING OUTPUT
 
 
 
-       Combining all three filter options would be the same result as  provid-
+       Combining  all three filter options would be the same result as provid-
        ing none of them.
 
 
 
-				   July 2017		    BUNDLE-OUTDATED(1)
+				 December 2018		    BUNDLE-OUTDATED(1)

data/man/bundle-outdated.ronn

@@ -15,6 +15,7 @@ bundle-outdated(1) -- List installed gems with newer versions available
                         [--filter-major]
                         [--filter-minor]
                         [--filter-patch]
+                        [--only-explicit]
 
 ## DESCRIPTION
 
@@ -67,9 +68,12 @@ are up to date, Bundler will exit with a status of 0. Otherwise, it will exit 1.
 * `--filter-patch`:
   Only list patch newer versions.
 
+* `--only-explicit`:
+  Only list gems specified in your Gemfile, not their dependencies.
+
 ## PATCH LEVEL OPTIONS
 
-See [bundle update(1)][bundle-update] for details.
+See [bundle update(1)](bundle-update.1.html) for details.
 
 One difference between the patch level options in `bundle update` and here is the `--strict` option.
 `--strict` was already an option on outdated before the patch level options were added. `--strict`

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 2017" "" ""
+.TH "BUNDLE\-PACKAGE" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application
@@ -19,7 +19,7 @@ Since Bundler 1\.2, the \fBbundle package\fR command can also package \fB:git\fR
 When using gems that have different packages for different platforms, Bundler 1\.8 and newer support caching of gems for other platforms where the Gemfile has been resolved (i\.e\. present in the lockfile) in \fBvendor/cache\fR\. This needs to be enabled via the \fB\-\-all\-platforms\fR option\. This setting will be remembered in your local bundler configuration\.
 .
 .SH "REMOTE FETCHING"
-By default, if you run [bundle install(1)][bundle\-install] after running [bundle package(1)][bundle\-package], bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
+By default, if you run \fBbundle install(1)\fR](bundle\-install\.1\.html) after running bundle package(1) \fIbundle\-package\.1\.html\fR, bundler will still connect to \fBrubygems\.org\fR to check whether a platform\-specific gem exists for any of the gems in \fBvendor/cache\fR\.
 .
 .P
 For instance, consider this Gemfile(5):
@@ -52,4 +52,4 @@ If you know for sure that the gems packaged in \fBvendor/cache\fR are appropriat
 One way to be sure that you have the right platformed versions of all your gems is to run \fBbundle package\fR on an identical machine and check in the gems\. For instance, you can run \fBbundle package\fR on an identical staging box during your staging process, and check in the \fBvendor/cache\fR before deploying to production\.
 .
 .P
-By default, [bundle package(1)][bundle\-package] fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.
+By default, bundle package(1) \fIbundle\-package\.1\.html\fR fetches and also installs the gems to the default location\. To package the dependencies to \fBvendor/cache\fR without installing them to the local install location, you can run \fBbundle package \-\-no\-install\fR\.

data/man/bundle-package.1.txt

@@ -28,10 +28,10 @@ SUPPORT FOR MULTIPLE PLATFORMS
        This setting will be remembered in your local bundler configuration.
 
 REMOTE FETCHING
-       By  default,  if you run [bundle install(1)][bundle-install] after run-
-       ning [bundle package(1)][bundle-package], bundler will still connect to
-       rubygems.org to check whether a platform-specific gem exists for any of
-       the gems in vendor/cache.
+       By  default, if you run bundle install(1)](bundle-install.1.html) after
+       running bundle package(1)  bundle-package.1.html,  bundler  will  still
+       connect to rubygems.org to check whether a platform-specific gem exists
+       for any of the gems in vendor/cache.
 
        For instance, consider this Gemfile(5):
 
@@ -69,11 +69,11 @@ REMOTE FETCHING
        staging	box during your staging process, and check in the vendor/cache
        before deploying to production.
 
-       By  default,  [bundle  package(1)][bundle-package]  fetches  and   also
+       By default, bundle package(1) bundle-package.1.html  fetches  and  also
        installs  the gems to the default location. To package the dependencies
        to vendor/cache without installing them to the local install  location,
        you can run bundle package --no-install.
 
 
 
-				September 2017		     BUNDLE-PACKAGE(1)
+				 November 2018		     BUNDLE-PACKAGE(1)

data/man/bundle-package.ronn

@@ -27,8 +27,8 @@ in your local bundler configuration.
 
 ## REMOTE FETCHING
 
-By default, if you run [bundle install(1)][bundle-install] after running
-[bundle package(1)][bundle-package], bundler will still connect to `rubygems.org`
+By default, if you run `bundle install(1)`](bundle-install.1.html) after running
+[bundle package(1)](bundle-package.1.html), bundler will still connect to `rubygems.org`
 to check whether a platform-specific gem exists for any of the gems
 in `vendor/cache`.
 
@@ -66,7 +66,7 @@ machine and check in the gems. For instance, you can run
 staging process, and check in the `vendor/cache` before
 deploying to production.
 
-By default, [bundle package(1)][bundle-package] fetches and also
+By default, [bundle package(1)](bundle-package.1.html) fetches and also
 installs the gems to the default location. To package the
 dependencies to `vendor/cache` without installing them to the
 local install location, you can run `bundle package --no-install`.

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" "February 2017" "" ""
+.TH "BUNDLE\-PLATFORM" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-platform\fR \- Displays platform compatibility information

data/man/bundle-platform.1.txt

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

data/man/bundle-pristine.1.txt

@@ -41,4 +41,4 @@ DESCRIPTION
 
 
 
-				  August 2017		    BUNDLE-PRISTINE(1)
+				 November 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" "December 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
+
+
+
+				 December 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" "February 2017" "" ""
+.TH "BUNDLE\-SHOW" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem
@@ -10,7 +10,7 @@
 \fBbundle show\fR [GEM] [\-\-paths]
 .
 .SH "DESCRIPTION"
-Without the [GEM] option, \fBshow\fR will print a list of the names and versions of all gems that are required by your \fBGemfile(5)\fR\.
+Without the [GEM] option, \fBshow\fR will print a list of the names and versions of all gems that are required by your [\fBGemfile(5)\fR][Gemfile(5)], sorted by name\.
 .
 .P
 Calling show with [GEM] will list the exact location of that gem on your machine\.
@@ -19,5 +19,5 @@ Calling show with [GEM] will list the exact location of that gem on your machine
 .
 .TP
 \fB\-\-paths\fR
-List the paths of all gems that are required by your \fBGemfile(5)\fR\.
+List the paths of all gems that are required by your [\fBGemfile(5)\fR][Gemfile(5)], sorted by gem name\.
 

data/man/bundle-show.1.txt

@@ -10,16 +10,18 @@ SYNOPSIS
 
 DESCRIPTION
        Without	the [GEM] option, show will print a list of the names and ver-
-       sions of all gems that are required by your Gemfile(5).
+       sions of all gems that are required by  your  [Gemfile(5)][Gemfile(5)],
+       sorted by name.
 
-       Calling show with [GEM] will list the exact location  of  that  gem  on
+       Calling	show  with  [GEM]  will list the exact location of that gem on
        your machine.
 
 OPTIONS
        --paths
-	      List the paths of all gems that are required by your Gemfile(5).
+	      List the paths of all gems  that	are  required  by  your  [Gem-
+	      file(5)][Gemfile(5)], sorted by gem name.
 
 
 
 
-				 February 2017			BUNDLE-SHOW(1)
+				 November 2018			BUNDLE-SHOW(1)

data/man/bundle-show.ronn

@@ -9,7 +9,7 @@ bundle-show(1) -- Shows all the gems in your bundle, or the path to a gem
 ## DESCRIPTION
 
 Without the [GEM] option, `show` will print a list of the names and versions of
-all gems that are required by your `Gemfile(5)`.
+all gems that are required by your [`Gemfile(5)`][Gemfile(5)], sorted by name.
 
 Calling show with [GEM] will list the exact location of that gem on your
 machine.
@@ -17,4 +17,5 @@ machine.
 ## OPTIONS
 
 * `--paths`:
-  List the paths of all gems that are required by your `Gemfile(5)`.
+  List the paths of all gems that are required by your [`Gemfile(5)`][Gemfile(5)],
+  sorted by gem name.

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" "July 2017" "" ""
+.TH "BUNDLE\-UPDATE" "1" "December 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)][bundle\-install] 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):
@@ -97,7 +101,7 @@ gem "nokogiri"
 .IP "" 0
 .
 .P
-When you run [bundle install(1)][bundle\-install] the first time, bundler will resolve all of the dependencies, all the way down, and install what you need:
+When you run bundle install(1) \fIbundle\-install\.1\.html\fR the first time, bundler will resolve all of the dependencies, all the way down, and install what you need:
 .
 .IP "" 4
 .
@@ -140,16 +144,16 @@ Use `bundle show [gemname]` to see where a bundled gem is installed\.
 .IP "" 0
 .
 .P
-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 \fBGemfile\.lock\fR\. The next time you run [bundle install(1)][bundle\-install], bundler skips the dependency resolution and installs the same gems as it installed last time\.
+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 \fBGemfile\.lock\fR\. The next time you run bundle install(1) \fIbundle\-install\.1\.html\fR, bundler skips the dependency resolution and installs the same gems as it installed last time\.
 .
 .P
-After checking in the \fBGemfile\.lock\fR into version control and cloning it on another machine, running [bundle install(1)][bundle\-install] will \fIstill\fR install the gems that you installed last time\. You don\'t need to worry that a new release of \fBerubis\fR or \fBmail\fR changes the gems you use\.
+After checking in the \fBGemfile\.lock\fR into version control and cloning it on another machine, running bundle install(1) \fIbundle\-install\.1\.html\fR will \fIstill\fR install the gems that you installed last time\. You don\'t need to worry that a new release of \fBerubis\fR or \fBmail\fR changes the gems you use\.
 .
 .P
 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\.
@@ -204,10 +208,10 @@ In this case, the two gems have their own set of dependencies, but they share \f
 In short, by default, when you update a gem using \fBbundle update\fR, bundler will update all dependencies of that gem, including those that are also dependencies of another gem\.
 .
 .P
-To prevent updating shared dependencies, prior to version 1\.14 the only option was the \fBCONSERVATIVE UPDATING\fR behavior in [bundle install(1)][bundle\-install]:
+To prevent updating shared dependencies, prior to version 1\.14 the only option was the \fBCONSERVATIVE UPDATING\fR behavior in bundle install(1) \fIbundle\-install\.1\.html\fR:
 .
 .P
-In this scenario, updating the \fBthin\fR version manually in the Gemfile(5), and then running [bundle install(1)][bundle\-install] will only update \fBdaemons\fR and \fBeventmachine\fR, but not \fBrack\fR\. For more information, see the \fBCONSERVATIVE UPDATING\fR section of [bundle install(1)][bundle\-install]\.
+In this scenario, updating the \fBthin\fR version manually in the Gemfile(5), and then running bundle install(1) \fIbundle\-install\.1\.html\fR will only update \fBdaemons\fR and \fBeventmachine\fR, but not \fBrack\fR\. For more information, see the \fBCONSERVATIVE UPDATING\fR section of bundle install(1) \fIbundle\-install\.1\.html\fR\.
 .
 .P
 Starting with 1\.14, specifying the \fB\-\-conservative\fR option will also prevent shared dependencies from being updated\.
@@ -375,7 +379,7 @@ Make sure to check the updated \fBGemfile\.lock\fR into version control
 $ git add Gemfile\.lock
 .
 .IP "\(bu" 4
-If [bundle install(1)][bundle\-install] reports a conflict, manually update the specific gems that you changed in the Gemfile(5)
+If bundle install(1) \fIbundle\-install\.1\.html\fR reports a conflict, manually update the specific gems that you changed in the Gemfile(5)
 .
 .IP
 $ bundle update rails thin
@@ -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