bundler 1.15.1 → 1.17.3

data/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,9 +19,9 @@ 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] to install the same exact
+general, 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
@@ -28,7 +29,10 @@ gem.
 
 ## OPTIONS
 
-* `--group=<name>`:
+* `--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
@@ -51,7 +55,7 @@ gem.
 * `--full-index`:
   Fall back to using the single-file index of all gems.
 
-* `--jobs=[<number>]`:
+* `--jobs=[<number>]`, `-j[<number>]`:
   Specify the number of jobs to run in parallel. The default is `1`.
 
 * `--retry=[<number>]`:
@@ -61,7 +65,7 @@ gem.
   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.
@@ -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.
 
@@ -91,7 +95,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.html) 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,21 +132,21 @@ 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.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] will _still_ install the gems that you installed
+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 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
 
@@ -192,12 +196,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.html):
 
 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.html) 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.html).
 
 Starting with 1.14, specifying the `--conservative` option will also prevent shared
 dependencies from being updated.
@@ -335,7 +339,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.html) reports a conflict, manually update the specific
   gems that you changed in the Gemfile(5)
 
     $ bundle update rails thin
@@ -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

data/man/bundle-viz.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-VIZ" "1" "May 2017" "" ""
+.TH "BUNDLE\-VIZ" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-viz\fR \- Generates a visual dependency graph for your Gemfile
@@ -13,27 +13,27 @@
 \fBviz\fR generates a PNG file of the current \fBGemfile(5)\fR as a dependency graph\. \fBviz\fR requires the ruby\-graphviz gem (and its dependencies)\.
 .
 .P
-The associated gems must also be installed via \fBbundle install(1)\fR\.
+The associated gems must also be installed via \fBbundle install(1)\fR \fIbundle\-install\.1\.html\fR\.
 .
 .SH "OPTIONS"
 .
 .TP
-\fB\-\-file\fR
+\fB\-\-file\fR, \fB\-f\fR
 The name to use for the generated file\. See \fB\-\-format\fR option
 .
 .TP
-\fB\-\-format\fR
+\fB\-\-format\fR, \fB\-F\fR
 This is output format option\. Supported format is png, jpg, svg, dot \.\.\.
 .
 .TP
-\fB\-\-requirements\fR
+\fB\-\-requirements\fR, \fB\-R\fR
 Set to show the version of each required dependency\.
 .
 .TP
-\fB\-\-version\fR
+\fB\-\-version\fR, \fB\-v\fR
 Set to show each gem version\.
 .
 .TP
-\fB\-\-without\fR
+\fB\-\-without\fR, \fB\-W\fR
 Exclude gems that are part of the specified named group\.
 

data/man/bundle-viz.1.txt

@@ -2,36 +2,38 @@ BUNDLE-VIZ(1)							 BUNDLE-VIZ(1)
 
 
 
-1mNAME0m
-       1mbundle-viz 22m- Generates a visual dependency graph for your Gemfile
+NAME
+       bundle-viz - Generates a visual dependency graph for your Gemfile
 
-1mSYNOPSIS0m
-       1mbundle viz 22m[--file=FILE] [--format=FORMAT] [--requirements] [--version]
+SYNOPSIS
+       bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version]
        [--without=GROUP GROUP]
 
-1mDESCRIPTION0m
-       1mviz 22mgenerates a PNG file of the  current  1mGemfile(5)  22mas  a  dependency
-       graph. 1mviz 22mrequires the ruby-graphviz gem (and its dependencies).
+DESCRIPTION
+       viz generates a PNG file of the	current  Gemfile(5)  as  a  dependency
+       graph. viz requires the ruby-graphviz gem (and its dependencies).
 
-       The associated gems must also be installed via 1mbundle install(1)22m.
+       The  associated	gems must also be installed via bundle install(1) bun-
+       dle-install.1.html.
 
-1mOPTIONS0m
-       1m--file 22mThe name to use for the generated file. See 1m--format 22moption
+OPTIONS
+       --file, -f
+	      The name to use for the generated file. See --format option
 
-       1m--format0m
+       --format, -F
 	      This is output format option. Supported format is png, jpg, svg,
 	      dot ...
 
-       1m--requirements0m
+       --requirements, -R
 	      Set to show the version of each required dependency.
 
-       1m--version0m
+       --version, -v
 	      Set to show each gem version.
 
-       1m--without0m
+       --without, -W
 	      Exclude gems that are part of the specified named group.
 
 
 
 
-				   May 2017			 BUNDLE-VIZ(1)
+				 November 2018			 BUNDLE-VIZ(1)

data/man/bundle-viz.ronn

@@ -14,17 +14,17 @@ bundle-viz(1) -- Generates a visual dependency graph for your Gemfile
 `viz` generates a PNG file of the current `Gemfile(5)` as a dependency graph.
 `viz` requires the ruby-graphviz gem (and its dependencies).
 
-The associated gems must also be installed via `bundle install(1)`.
+The associated gems must also be installed via [`bundle install(1)`](bundle-install.1.html).
 
 ## OPTIONS
 
-* `--file`:
+* `--file`, `-f`:
   The name to use for the generated file. See `--format` option
-* `--format`:
+* `--format`, `-F`:
   This is output format option. Supported format is png, jpg, svg, dot ...
-* `--requirements`:
+* `--requirements`, `-R`:
   Set to show the version of each required dependency.
-* `--version`:
+* `--version`, `-v`:
   Set to show each gem version.
-* `--without`:
+* `--without`, `-W`:
   Exclude gems that are part of the specified named group.

data/man/bundle.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE" "1" "June 2017" "" ""
+.TH "BUNDLE" "1" "December 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\fR \- Ruby Dependency Management
@@ -22,11 +22,15 @@ See the bundler website \fIhttp://bundler\.io\fR for information on getting star
 Print all output without color
 .
 .TP
-\fB\-\-verbose\fR
+\fB\-\-retry\fR, \fB\-r\fR
+Specify the number of times you wish to attempt network commands
+.
+.TP
+\fB\-\-verbose\fR, \fB\-V\fR
 Print out additional logging information
 .
 .SH "BUNDLE COMMANDS"
-We divide \fBbundle\fR subcommands into primary commands and utilities\.
+We divide \fBbundle\fR subcommands into primary commands and utilities:
 .
 .SH "PRIMARY COMMANDS"
 .
@@ -44,11 +48,11 @@ Package the \.gem files required by your application into the \fBvendor/cache\fR
 .
 .TP
 \fBbundle exec(1)\fR \fIbundle\-exec\.1\.html\fR
-Execute a script in the context of the current bundle
+Execute a script in the current bundle
 .
 .TP
 \fBbundle config(1)\fR \fIbundle\-config\.1\.html\fR
-Specify and read configuration options for bundler
+Specify and read configuration options for Bundler
 .
 .TP
 \fBbundle help(1)\fR
@@ -57,81 +61,76 @@ Display detailed help for each subcommand
 .SH "UTILITIES"
 .
 .TP
-\fBbundle add(1)\fR
+\fBbundle add(1)\fR \fIbundle\-add\.1\.html\fR
 Add the named gem to the Gemfile and run \fBbundle install\fR
 .
 .TP
-\fBbundle binstubs(1)\fR
+\fBbundle binstubs(1)\fR \fIbundle\-binstubs\.1\.html\fR
 Generate binstubs for executables in a gem
 .
 .TP
-\fBbundle check(1)\fR
-Determine whether the requirements for your application are installed and available to bundler
+\fBbundle check(1)\fR \fIbundle\-check\.1\.html\fR
+Determine whether the requirements for your application are installed and available to Bundler
 .
 .TP
-\fBbundle show(1)\fR
+\fBbundle show(1)\fR \fIbundle\-show\.1\.html\fR
 Show the source location of a particular gem in the bundle
 .
 .TP
-[\fBbundle outdated(1)\fR][bundle\-outdated]
+\fBbundle outdated(1)\fR \fIbundle\-outdated\.1\.html\fR
 Show all of the outdated gems in the current bundle
 .
 .TP
 \fBbundle console(1)\fR
-Start an IRB session in the context of the current bundle
+Start an IRB session in the current bundle
 .
 .TP
-\fBbundle open(1)\fR
+\fBbundle open(1)\fR \fIbundle\-open\.1\.html\fR
 Open an installed gem in the editor
 .
 .TP
-[\fBbundle lock(1)\fR][bundle\-lock]
+\fBbundle lock(1)\fR \fIbundle\-lock\.1\.hmtl\fR
 Generate a lockfile for your dependencies
 .
 .TP
-\fBbundle viz(1)\fR
+\fBbundle viz(1)\fR \fIbundle\-viz\.1\.html\fR
 Generate a visual representation of your dependencies
 .
 .TP
-\fBbundle init(1)\fR
+\fBbundle init(1)\fR \fIbundle\-init\.1\.html\fR
 Generate a simple \fBGemfile\fR, placed in the current directory
 .
 .TP
 \fBbundle gem(1)\fR \fIbundle\-gem\.1\.html\fR
-Create a simple gem, suitable for development with bundler
+Create a simple gem, suitable for development with Bundler
 .
 .TP
 \fBbundle platform(1)\fR \fIbundle\-platform\.1\.html\fR
 Display platform compatibility information
 .
 .TP
-\fBbundle clean(1)\fR
-Clean up unused gems in your bundler directory
+\fBbundle clean(1)\fR \fIbundle\-clean\.1\.html\fR
+Clean up unused gems in your Bundler directory
 .
 .TP
-\fBbundle doctor(1)\fR
-Display warnings about common potential problems
+\fBbundle doctor(1)\fR \fIbundle\-doctor\.1\.html\fR
+Display warnings about common problems
+.
+.TP
+\fBbundle remove(1)\fR \fIbundle\-remove\.1\.html\fR
+Removes gems from the Gemfile
 .
 .SH "PLUGINS"
 When running a command that isn\'t listed in PRIMARY COMMANDS or UTILITIES, Bundler will try to find an executable on your path named \fBbundler\-<command>\fR and execute it, passing down any extra arguments to it\.
 .
-.SH "BUNDLER TRAMPOLINING"
-Bundler includes a feature called trampolining, designed to allow a single developer to work on multiple projects, each on different Bundler versions\. The trampoline will infer the correct version of Bundler to use for each project and load that version instead of the version directly invoked (which is almost always the newest version installed locally)\.
-.
-.P
-Bundler by default will use the Bundler version in the current directory to determine the version to trampoline to, reading from the \fBBUNDLED WITH\fR section\. However, if the \fBBUNDLER_VERSION\fR environment variable is set, that version will override the lockfile inference and can be used in directories without a lockfile\.
-.
-.P
-Until the target version is Bundler 2 or later, \fBBUNDLE_TRAMPOLINE_FORCE\fR must be set for the trampoline to be used\. Additionally, \fBBUNDLE_TRAMPOLINE_DISABLE\fR can be set to completely disable the trampoline\.
-.
 .SH "OBSOLETE"
-These commands are obsolete and should no longer be used
+These commands are obsolete and should no longer be used:
 .
 .IP "\(bu" 4
 \fBbundle cache(1)\fR
 .
 .IP "\(bu" 4
-\fBbundle list(1)\fR
+\fBbundle show(1)\fR
 .
 .IP "" 0
 

data/man/bundle.1.txt

@@ -2,127 +2,115 @@ BUNDLE(1)							     BUNDLE(1)
 
 
 
-1mNAME0m
-       1mbundle 22m- Ruby Dependency Management
+NAME
+       bundle - Ruby Dependency Management
 
-1mSYNOPSIS0m
-       1mbundle 22mCOMMAND [--no-color] [--verbose] [ARGS]
+SYNOPSIS
+       bundle COMMAND [--no-color] [--verbose] [ARGS]
 
-1mDESCRIPTION0m
-       Bundler	manages  an 1mapplication's dependencies 22mthrough its entire life
+DESCRIPTION
+       Bundler	manages  an application's dependencies through its entire life
        across many machines systematically and repeatably.
 
-       See the bundler website 4mhttp://bundler.io24m for  information	on  getting
-       started, and Gemfile(5) for more information on the 1mGemfile 22mformat.
+       See the bundler website http://bundler.io for  information  on  getting
+       started, and Gemfile(5) for more information on the Gemfile format.
 
-1mOPTIONS0m
-       1m--no-color0m
+OPTIONS
+       --no-color
 	      Print all output without color
 
-       1m--verbose0m
+       --retry, -r
+	      Specify the number of times you wish to attempt network commands
+
+       --verbose, -V
 	      Print out additional logging information
 
-1mBUNDLE COMMANDS0m
-       We divide 1mbundle 22msubcommands into primary commands and utilities.
+BUNDLE COMMANDS
+       We divide bundle subcommands into primary commands and utilities:
 
-1mPRIMARY COMMANDS0m
-       1mbundle install(1) 4m22mbundle-install.1.html0m
-	      Install the gems specified by the 1mGemfile 22mor 1mGemfile.lock0m
+PRIMARY COMMANDS
+       bundle install(1) bundle-install.1.html
+	      Install the gems specified by the Gemfile or Gemfile.lock
 
-       1mbundle update(1) 4m22mbundle-update.1.html0m
+       bundle update(1) bundle-update.1.html
 	      Update dependencies to their latest versions
 
-       1mbundle package(1) 4m22mbundle-package.1.html0m
-	      Package  the  .gem  files  required by your application into the
-	      1mvendor/cache 22mdirectory
+       bundle package(1) bundle-package.1.html
+	      Package the .gem files required by  your	application  into  the
+	      vendor/cache directory
 
-       1mbundle exec(1) 4m22mbundle-exec.1.html0m
-	      Execute a script in the context of the current bundle
+       bundle exec(1) bundle-exec.1.html
+	      Execute a script in the current bundle
 
-       1mbundle config(1) 4m22mbundle-config.1.html0m
-	      Specify and read configuration options for bundler
+       bundle config(1) bundle-config.1.html
+	      Specify and read configuration options for Bundler
 
-       1mbundle help(1)0m
+       bundle help(1)
 	      Display detailed help for each subcommand
 
-1mUTILITIES0m
-       1mbundle add(1)0m
-	      Add the named gem to the Gemfile and run 1mbundle install0m
+UTILITIES
+       bundle add(1) bundle-add.1.html
+	      Add the named gem to the Gemfile and run bundle install
 
-       1mbundle binstubs(1)0m
+       bundle binstubs(1) bundle-binstubs.1.html
 	      Generate binstubs for executables in a gem
 
-       1mbundle check(1)0m
-	      Determine whether the  requirements  for	your  application  are
-	      installed and available to bundler
+       bundle check(1) bundle-check.1.html
+	      Determine  whether  the  requirements  for  your application are
+	      installed and available to Bundler
 
-       1mbundle show(1)0m
+       bundle show(1) bundle-show.1.html
 	      Show the source location of a particular gem in the bundle
 
-       [1mbundle outdated(1)22m][bundle-outdated]
+       bundle outdated(1) bundle-outdated.1.html
 	      Show all of the outdated gems in the current bundle
 
-       1mbundle console(1)0m
-	      Start an IRB session in the context of the current bundle
+       bundle console(1)
+	      Start an IRB session in the current bundle
 
-       1mbundle open(1)0m
+       bundle open(1) bundle-open.1.html
 	      Open an installed gem in the editor
 
-       [1mbundle lock(1)22m][bundle-lock]
+       bundle lock(1) bundle-lock.1.hmtl
 	      Generate a lockfile for your dependencies
 
-       1mbundle viz(1)0m
+       bundle viz(1) bundle-viz.1.html
 	      Generate a visual representation of your dependencies
 
-       1mbundle init(1)0m
-	      Generate a simple 1mGemfile22m, placed in the current directory
+       bundle init(1) bundle-init.1.html
+	      Generate a simple Gemfile, placed in the current directory
 
-       1mbundle gem(1) 4m22mbundle-gem.1.html0m
-	      Create a simple gem, suitable for development with bundler
+       bundle gem(1) bundle-gem.1.html
+	      Create a simple gem, suitable for development with Bundler
 
-       1mbundle platform(1) 4m22mbundle-platform.1.html0m
+       bundle platform(1) bundle-platform.1.html
 	      Display platform compatibility information
 
-       1mbundle clean(1)0m
-	      Clean up unused gems in your bundler directory
-
-       1mbundle doctor(1)0m
-	      Display warnings about common potential problems
+       bundle clean(1) bundle-clean.1.html
+	      Clean up unused gems in your Bundler directory
 
-1mPLUGINS0m
-       When  running a command that isn't listed in PRIMARY COMMANDS or UTILI-
-       TIES, Bundler will try  to  find  an  executable  on  your  path  named
-       1mbundler-<command>  22mand  execute it, passing down any extra arguments to
-       it.
+       bundle doctor(1) bundle-doctor.1.html
+	      Display warnings about common problems
 
-1mBUNDLER TRAMPOLINING0m
-       Bundler includes a feature called trampolining,	designed  to  allow  a
-       single  developer  to  work  on	multiple  projects,  each on different
-       Bundler versions. The trampoline will  infer  the  correct  version  of
-       Bundler	to  use  for each project and load that version instead of the
-       version directly invoked (which is almost  always  the  newest  version
-       installed locally).
+       bundle remove(1) bundle-remove.1.html
+	      Removes gems from the Gemfile
 
-       Bundler	by  default will use the Bundler version in the current direc-
-       tory to determine the version to trampoline to, reading from  the  1mBUN-0m
-       1mDLED WITH 22msection. However, if the 1mBUNDLER_VERSION 22menvironment variable
-       is set, that version will override the lockfile inference  and  can  be
-       used in directories without a lockfile.
-
-       Until the target version is Bundler 2 or later, 1mBUNDLE_TRAMPOLINE_FORCE0m
-       must be set for the trampoline to be used. Additionally, 1mBUNDLE_TRAMPO-0m
-       1mLINE_DISABLE 22mcan be set to completely disable the trampoline.
+PLUGINS
+       When running a command that isn't listed in PRIMARY COMMANDS or	UTILI-
+       TIES,  Bundler  will  try  to  find  an	executable  on your path named
+       bundler-<command> and execute it, passing down any extra  arguments  to
+       it.
 
-1mOBSOLETE0m
-       These commands are obsolete and should no longer be used
+OBSOLETE
+       These commands are obsolete and should no longer be used:
 
-       o   1mbundle cache(1)0m
+       o   bundle cache(1)
 
-       o   1mbundle list(1)0m
+       o   bundle show(1)
 
 
 
 
 
 
-				   June 2017			     BUNDLE(1)
+				 December 2018			     BUNDLE(1)