bundler 1.16.1 → 1.16.2

data/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

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" "February 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][bundle\-install(1)]\.
 .
 .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)].
 
 OPTIONS
        --file, -f
@@ -35,4 +36,4 @@ OPTIONS
 
 
 
-				   July 2017			 BUNDLE-VIZ(1)
+				 February 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)].
 
 ## 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" "May 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][bundle\-install(1)]
 Install the gems specified by the \fBGemfile\fR or \fBGemfile\.lock\fR
 .
 .TP
-[\fBbundle update(1)\fR][bundle\-update]
+[\fBbundle update(1)\fR][bundle\-update(1)]
 Update dependencies to their latest versions
 .
 .TP
-[\fBbundle package(1)\fR][bundle\-package]
+[\fBbundle package(1)\fR][bundle\-package(1)]
 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][bundle\-exec(1)]
+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][bundle\-config(1)]
+Specify and read configuration options for Bundler
 .
 .TP
 \fBbundle help(1)\fR
@@ -61,31 +61,31 @@ Display detailed help for each subcommand
 .SH "UTILITIES"
 .
 .TP
-\fBbundle add(1)\fR
+[\fBbundle add(1)\fR][bundle\-add(1)]
 Add the named gem to the Gemfile and run \fBbundle install\fR
 .
 .TP
-\fBbundle binstubs(1)\fR
+[\fBbundle binstubs(1)\fR][bundle\-binstubs(1)]
 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][bundle\-check(1)]
+Determine whether the requirements for your application are installed and available to Bundler
 .
 .TP
-\fBbundle show(1)\fR
+[\fBbundle show(1)\fR][bundle\-show(1)]
 Show the source location of a particular gem in the bundle
 .
 .TP
-[\fBbundle outdated(1)\fR][bundle\-outdated]
+[\fBbundle outdated(1)\fR][bundle\-outdated(1)]
 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][bundle\-open(1)]
 Open an installed gem in the editor
 .
 .TP
@@ -93,34 +93,34 @@ Open an installed gem in the editor
 Generate a lockfile for your dependencies
 .
 .TP
-\fBbundle viz(1)\fR
+[\fBbundle viz(1)\fR][bundle\-viz(1)]
 Generate a visual representation of your dependencies
 .
 .TP
-\fBbundle init(1)\fR
+[\fBbundle init(1)\fR][bundle\-init(1)]
 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][bundle\-gem(1)]
+Create a simple gem, suitable for development with Bundler
 .
 .TP
-[\fBbundle platform(1)\fR][bundle\-platform]
+[\fBbundle platform(1)\fR][bundle\-platform(1)]
 Display platform compatibility information
 .
 .TP
-\fBbundle clean(1)\fR
-Clean up unused gems in your bundler directory
+[\fBbundle clean(1)\fR][bundle\-clean(1)]
+Clean up unused gems in your Bundler directory
 .
 .TP
 \fBbundle doctor(1)\fR
-Display warnings about common potential problems
+Display warnings about common problems
 .
 .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

data/man/bundle.1.txt

@@ -26,71 +26,71 @@ OPTIONS
 	      Print out additional logging information
 
 BUNDLE COMMANDS
-       We divide bundle subcommands into primary commands and utilities.
+       We divide bundle subcommands into primary commands and utilities:
 
 PRIMARY COMMANDS
-       [bundle install(1)][bundle-install]
+       [bundle install(1)][bundle-install(1)]
 	      Install the gems specified by the Gemfile or Gemfile.lock
 
-       [bundle update(1)][bundle-update]
+       [bundle update(1)][bundle-update(1)]
 	      Update dependencies to their latest versions
 
-       [bundle package(1)][bundle-package]
+       [bundle package(1)][bundle-package(1)]
 	      Package the .gem files required by  your	application  into  the
 	      vendor/cache directory
 
-       [bundle exec(1)][bundle-exec]
-	      Execute a script in the context of the current bundle
+       [bundle exec(1)][bundle-exec(1)]
+	      Execute a script in the current bundle
 
-       [bundle config(1)][bundle-config]
-	      Specify and read configuration options for bundler
+       [bundle config(1)][bundle-config(1)]
+	      Specify and read configuration options for Bundler
 
        bundle help(1)
 	      Display detailed help for each subcommand
 
 UTILITIES
-       bundle add(1)
+       [bundle add(1)][bundle-add(1)]
 	      Add the named gem to the Gemfile and run bundle install
 
-       bundle binstubs(1)
+       [bundle binstubs(1)][bundle-binstubs(1)]
 	      Generate binstubs for executables in a gem
 
-       bundle check(1)
+       [bundle check(1)][bundle-check(1)]
 	      Determine  whether  the  requirements  for  your application are
-	      installed and available to bundler
+	      installed and available to Bundler
 
-       bundle show(1)
+       [bundle show(1)][bundle-show(1)]
 	      Show the source location of a particular gem in the bundle
 
-       [bundle outdated(1)][bundle-outdated]
+       [bundle outdated(1)][bundle-outdated(1)]
 	      Show all of the outdated gems in the current bundle
 
        bundle console(1)
-	      Start an IRB session in the context of the current bundle
+	      Start an IRB session in the current bundle
 
-       bundle open(1)
+       [bundle open(1)][bundle-open(1)]
 	      Open an installed gem in the editor
 
        [bundle lock(1)][bundle-lock]
 	      Generate a lockfile for your dependencies
 
-       bundle viz(1)
+       [bundle viz(1)][bundle-viz(1)]
 	      Generate a visual representation of your dependencies
 
-       bundle init(1)
+       [bundle init(1)][bundle-init(1)]
 	      Generate a simple Gemfile, placed in the current directory
 
-       [bundle gem(1)][bundle-gem]
-	      Create a simple gem, suitable for development with bundler
+       [bundle gem(1)][bundle-gem(1)]
+	      Create a simple gem, suitable for development with Bundler
 
-       [bundle platform(1)][bundle-platform]
+       [bundle platform(1)][bundle-platform(1)]
 	      Display platform compatibility information
 
-       bundle clean(1)
-	      Clean up unused gems in your bundler directory
+       [bundle clean(1)][bundle-clean(1)]
+	      Clean up unused gems in your Bundler directory
 
        bundle doctor(1)
-	      Display warnings about common potential problems
+	      Display warnings about common problems
 
 PLUGINS
        When running a command that isn't listed in PRIMARY COMMANDS or	UTILI-
@@ -99,7 +99,7 @@ PLUGINS
        it.
 
 OBSOLETE
-       These commands are obsolete and should no longer be used
+       These commands are obsolete and should no longer be used:
 
        o   bundle cache(1)
 
@@ -110,4 +110,4 @@ OBSOLETE
 
 
 
-				   July 2017			     BUNDLE(1)
+				   May 2018			     BUNDLE(1)

data/man/bundle.ronn

@@ -26,73 +26,73 @@ started, and Gemfile(5) for more information on the `Gemfile` format.
 
 ## BUNDLE COMMANDS
 
-We divide `bundle` subcommands into primary commands and utilities.
+We divide `bundle` subcommands into primary commands and utilities:
 
 ## PRIMARY COMMANDS
 
-* [`bundle install(1)`][bundle-install]:
+* [`bundle install(1)`][bundle-install(1)]:
   Install the gems specified by the `Gemfile` or `Gemfile.lock`
 
-* [`bundle update(1)`][bundle-update]:
+* [`bundle update(1)`][bundle-update(1)]:
   Update dependencies to their latest versions
 
-* [`bundle package(1)`][bundle-package]:
+* [`bundle package(1)`][bundle-package(1)]:
   Package the .gem files required by your application into the
   `vendor/cache` directory
 
-* [`bundle exec(1)`][bundle-exec]:
-  Execute a script in the context of the current bundle
+* [`bundle exec(1)`][bundle-exec(1)]:
+  Execute a script in the current bundle
 
-* [`bundle config(1)`][bundle-config]:
-  Specify and read configuration options for bundler
+* [`bundle config(1)`][bundle-config(1)]:
+  Specify and read configuration options for Bundler
 
 * `bundle help(1)`:
   Display detailed help for each subcommand
 
 ## UTILITIES
 
-* `bundle add(1)`:
+* [`bundle add(1)`][bundle-add(1)]:
   Add the named gem to the Gemfile and run `bundle install`
 
-* `bundle binstubs(1)`:
+* [`bundle binstubs(1)`][bundle-binstubs(1)]:
   Generate binstubs for executables in a gem
 
-* `bundle check(1)`:
+* [`bundle check(1)`][bundle-check(1)]:
   Determine whether the requirements for your application are installed
-  and available to bundler
+  and available to Bundler
 
-* `bundle show(1)`:
+* [`bundle show(1)`][bundle-show(1)]:
   Show the source location of a particular gem in the bundle
 
-* [`bundle outdated(1)`][bundle-outdated]:
+* [`bundle outdated(1)`][bundle-outdated(1)]:
   Show all of the outdated gems in the current bundle
 
 * `bundle console(1)`:
-  Start an IRB session in the context of the current bundle
+  Start an IRB session in the current bundle
 
-* `bundle open(1)`:
+* [`bundle open(1)`][bundle-open(1)]:
   Open an installed gem in the editor
 
 * [`bundle lock(1)`][bundle-lock]:
   Generate a lockfile for your dependencies
 
-* `bundle viz(1)`:
+* [`bundle viz(1)`][bundle-viz(1)]:
   Generate a visual representation of your dependencies
 
-* `bundle init(1)`:
+* [`bundle init(1)`][bundle-init(1)]:
   Generate a simple `Gemfile`, placed in the current directory
 
-* [`bundle gem(1)`][bundle-gem]:
-  Create a simple gem, suitable for development with bundler
+* [`bundle gem(1)`][bundle-gem(1)]:
+  Create a simple gem, suitable for development with Bundler
 
-* [`bundle platform(1)`][bundle-platform]:
+* [`bundle platform(1)`][bundle-platform(1)]:
   Display platform compatibility information
 
-* `bundle clean(1)`:
-  Clean up unused gems in your bundler directory
+* [`bundle clean(1)`][bundle-clean(1)]:
+  Clean up unused gems in your Bundler directory
 
 * `bundle doctor(1)`:
-  Display warnings about common potential problems
+  Display warnings about common problems
 
 ## PLUGINS
 
@@ -102,7 +102,7 @@ and execute it, passing down any extra arguments to it.
 
 ## OBSOLETE
 
-These commands are obsolete and should no longer be used
+These commands are obsolete and should no longer be used:
 
 * `bundle cache(1)`
 * `bundle show(1)`

data/man/gemfile.5

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "GEMFILE" "5" "July 2017" "" ""
+.TH "GEMFILE" "5" "February 2018" "" ""
 .
 .SH "NAME"
 \fBGemfile\fR \- A format for describing gem dependencies for Ruby programs
@@ -35,7 +35,7 @@ It is possible, but not recommended as of Bundler 1\.7, to add multiple global \
 Sources are checked for gems following the heuristics described in \fISOURCE PRIORITY\fR\. If a gem is found in more than one global source, Bundler will print a warning after installing the gem indicating which source was used, and listing the other sources where the gem is available\. A specific source can be selected for gems that need to use a non\-standard repository, suppressing this warning, by using the \fI\fB:source\fR option\fR or a \fI\fBsource\fR block\fR\.
 .
 .SS "CREDENTIALS"
-Some gem sources require a username and password\. Use [bundle config(1)][bundle\-config] to set the username and password for any of the sources that need it\. The command must be run once on each computer that will install the Gemfile, but this keeps the credentials from being stored in plain text in version control\.
+Some gem sources require a username and password\. Use [bundle config(1)][bundle\-config(1)] to set the username and password for any of the sources that need it\. The command must be run once on each computer that will install the Gemfile, but this keeps the credentials from being stored in plain text in version control\.
 .
 .IP "" 4
 .
@@ -325,7 +325,7 @@ gem "nokogiri",   :platforms => [:mri_18, :jruby]
 .IP "" 0
 .
 .P
-All operations involving groups (\fBbundle install\fR, \fBBundler\.setup\fR, \fBBundler\.require\fR) behave exactly the same as if any groups not matching the current platform were explicitly excluded\.
+All operations involving groups ([\fBbundle install\fR][bundle\-install(1)], \fBBundler\.setup\fR, \fBBundler\.require\fR) behave exactly the same as if any groups not matching the current platform were explicitly excluded\.
 .
 .SS "SOURCE"
 You can select an alternate Rubygems repository for a gem using the \':source\' option\.
@@ -649,7 +649,7 @@ end
 .IP "" 0
 .
 .SH "GEMSPEC"
-The \.gemspec \fIhttp://guides\.rubygems\.org/specification\-reference/\fR file is where you provide metadata about your gem to Rubygems\. Some required Gemspec attributes include the name, description, and homepage of your gem\. This is also where you specify the dependencies your gem needs to run\.
+The \fB\.gemspec\fR \fIhttp://guides\.rubygems\.org/specification\-reference/\fR file is where you provide metadata about your gem to Rubygems\. Some required Gemspec attributes include the name, description, and homepage of your gem\. This is also where you specify the dependencies your gem needs to run\.
 .
 .P
 If you wish to use Bundler to help install dependencies for a gem while it is being developed, use the \fBgemspec\fR method to pull in the dependencies listed in the \fB\.gemspec\fR file\.