diff options
Diffstat (limited to 'man/bundle-update.ronn')
| -rw-r--r-- | man/bundle-update.ronn | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/man/bundle-update.ronn b/man/bundle-update.ronn index b29965985b..413a446c60 100644 --- a/man/bundle-update.ronn +++ b/man/bundle-update.ronn @@ -20,7 +20,7 @@ bundle-update(1) -- Update your gems to the latest available versions Update the gems specified (all gems, if none are specified), ignoring the previously installed gems specified in the `Gemfile.lock`. In -general, you should use [bundle install(1)][bundle-install] to install the same exact +general, you should use [bundle install(1)][bundle-install(1)] to install the same exact gems and versions across machines. You would use `bundle update` to explicitly update the version of a @@ -91,7 +91,7 @@ Consider the following Gemfile(5): gem "rails", "3.0.0.rc" gem "nokogiri" -When you run [bundle install(1)][bundle-install] the first time, bundler will resolve +When you run [bundle install(1)][bundle-install(1)] the first time, bundler will resolve all of the dependencies, all the way down, and install what you need: Fetching gem metadata from https://rubygems.org/......... @@ -128,11 +128,11 @@ all of the dependencies, all the way down, and install what you need: 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], bundler skips +it installed in `Gemfile.lock`. The next time you run [bundle install(1)][bundle-install(1)], 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] will _still_ install the gems that you installed +machine, running [bundle install(1)][bundle-install(1)] 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. @@ -192,12 +192,12 @@ 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 option -was the `CONSERVATIVE UPDATING` behavior in [bundle install(1)][bundle-install]: +was the `CONSERVATIVE UPDATING` behavior in [bundle install(1)][bundle-install(1)]: In this scenario, updating the `thin` version manually in the Gemfile(5), -and then running [bundle install(1)][bundle-install] will only update `daemons` and `eventmachine`, +and then running [bundle install(1)][bundle-install(1)] will only update `daemons` and `eventmachine`, but not `rack`. For more information, see the `CONSERVATIVE UPDATING` section -of [bundle install(1)][bundle-install]. +of [bundle install(1)][bundle-install(1)]. Starting with 1.14, specifying the `--conservative` option will also prevent shared dependencies from being updated. @@ -335,7 +335,7 @@ use the following workflow: $ git add Gemfile.lock -* If [bundle install(1)][bundle-install] reports a conflict, manually update the specific +* If [bundle install(1)][bundle-install(1)] reports a conflict, manually update the specific gems that you changed in the Gemfile(5) $ bundle update rails thin |