From 5f6107fc8d0c32d1c07d4b6c741008525c7ce8d7 Mon Sep 17 00:00:00 2001 From: Agrim Mittal Date: Thu, 19 Apr 2018 00:31:32 +0530 Subject: Add documentation for --all flag of bundle update --- man/bundle-update.ronn | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/man/bundle-update.ronn b/man/bundle-update.ronn index 413a446c60..493986a7a4 100644 --- a/man/bundle-update.ronn +++ b/man/bundle-update.ronn @@ -3,7 +3,8 @@ bundle-update(1) -- Update your gems to the latest available versions ## SYNOPSIS -`bundle update` <*gems> [--group=NAME] +`bundle update` <*gems> [--all] + [--group=NAME] [--source=NAME] [--local] [--ruby] @@ -18,7 +19,7 @@ bundle-update(1) -- Update your gems to the latest available versions ## 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 general, you should use [bundle install(1)][bundle-install(1)] to install the same exact gems and versions across machines. @@ -28,6 +29,9 @@ gem. ## OPTIONS +* `--all`: + Update all gems specified in Gemfile. + * `--group=`, `-g=[]`: 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 @@ -80,7 +84,7 @@ gem. ## UPDATING ALL GEMS -If you run `bundle update` with no parameters, bundler will ignore +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. @@ -139,10 +143,10 @@ 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 Gemfile(5). -To do this, run `bundle update`, which will ignore the `Gemfile.lock`, and resolve +To do this, run `bundle update --all`, 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`. +authors released since the last time you ran `bundle update --all`. ## UPDATING A LIST OF GEMS @@ -343,4 +347,4 @@ use the following workflow: * 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 -- cgit v1.2.1