bundler 1.16.1 → 1.17.3

data/man/bundle-update.1.txt

@@ -6,19 +6,21 @@ 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] to install the
-       same exact gems and versions across machines.
+       eral, 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  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]  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,26 +134,27 @@ 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], bundler skips the dependency reso-
-       lution 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 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 last time. You don't need  to
-       worry that a new release of erubis or mail changes the gems you use.
+       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-
        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
@@ -207,20 +211,21 @@ OVERLAPPING DEPENDENCIES
        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]:
+       option was the CONSERVATIVE UPDATING behavior in bundle install(1) bun-
+       dle-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, but not rack. For more information,  see  the
-       CONSERVATIVE UPDATING section of [bundle install(1)][bundle-install].
+       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.
 
        Starting with 1.14, specifying the --conservative option will also pre-
        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.
 
@@ -237,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
@@ -320,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
@@ -350,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
@@ -359,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
@@ -368,19 +373,19 @@ RECOMMENDED WORKFLOW
 
 	   $ git add Gemfile.lock
 
-       o   If [bundle install(1)][bundle-install] reports a conflict, manually
-	   update the specific gems that you changed in the Gemfile(5)
+       o   If bundle install(1) bundle-install.1.html reports a conflict, man-
+	   ually update the specific gems that you changed in the Gemfile(5)
 
 	   $ 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
 
 
 
 
 
 
-				   July 2017		      BUNDLE-UPDATE(1)
+				 December 2018		      BUNDLE-UPDATE(1)

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,6 +29,9 @@ 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 --group development`. You can also
@@ -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" "July 2017" "" ""
+.TH "BUNDLE\-VIZ" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-viz\fR \- Generates a visual dependency graph for your Gemfile
@@ -13,7 +13,7 @@
 \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"
 .

data/man/bundle-viz.1.txt

@@ -13,7 +13,8 @@ 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 bundle install(1).
+       The  associated	gems must also be installed via bundle install(1) bun-
+       dle-install.1.html.
 
 OPTIONS
        --file, -f
@@ -35,4 +36,4 @@ OPTIONS
 
 
 
-				   July 2017			 BUNDLE-VIZ(1)
+				 November 2018			 BUNDLE-VIZ(1)

data/man/bundle-viz.ronn

@@ -14,7 +14,7 @@ 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
 

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" "July 2017" "" ""
+.TH "BUNDLE" "1" "December 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\fR \- Ruby Dependency Management
@@ -30,29 +30,29 @@ Specify the number of times you wish to attempt network commands
 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"
 .
 .TP
-[\fBbundle install(1)\fR][bundle\-install]
+\fBbundle install(1)\fR \fIbundle\-install\.1\.html\fR
 Install the gems specified by the \fBGemfile\fR or \fBGemfile\.lock\fR
 .
 .TP
-[\fBbundle update(1)\fR][bundle\-update]
+\fBbundle update(1)\fR \fIbundle\-update\.1\.html\fR
 Update dependencies to their latest versions
 .
 .TP
-[\fBbundle package(1)\fR][bundle\-package]
+\fBbundle package(1)\fR \fIbundle\-package\.1\.html\fR
 Package the \.gem files required by your application into the \fBvendor/cache\fR directory
 .
 .TP
-[\fBbundle exec(1)\fR][bundle\-exec]
-Execute a script in the context of the current bundle
+\fBbundle exec(1)\fR \fIbundle\-exec\.1\.html\fR
+Execute a script in the current bundle
 .
 .TP
-[\fBbundle config(1)\fR][bundle\-config]
-Specify and read configuration options for bundler
+\fBbundle config(1)\fR \fIbundle\-config\.1\.html\fR
+Specify and read configuration options for Bundler
 .
 .TP
 \fBbundle help(1)\fR
@@ -61,66 +61,70 @@ 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][bundle\-gem]
-Create a simple gem, suitable for development with bundler
+\fBbundle gem(1)\fR \fIbundle\-gem\.1\.html\fR
+Create a simple gem, suitable for development with Bundler
 .
 .TP
-[\fBbundle platform(1)\fR][bundle\-platform]
+\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 \fIbundle\-doctor\.1\.html\fR
+Display warnings about common problems
 .
 .TP
-\fBbundle doctor(1)\fR
-Display warnings about common potential problems
+\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 "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