bundler 1.16.2 → 1.16.3

data/man/bundle.1.txt

@@ -29,67 +29,67 @@ BUNDLE COMMANDS
        We divide bundle subcommands into primary commands and utilities:
 
 PRIMARY COMMANDS
-       [bundle install(1)][bundle-install(1)]
+       bundle install(1) bundle-install.1.html
 	      Install the gems specified by the Gemfile or Gemfile.lock
 
-       [bundle update(1)][bundle-update(1)]
+       bundle update(1) bundle-update.1.html
 	      Update dependencies to their latest versions
 
-       [bundle package(1)][bundle-package(1)]
+       bundle package(1) bundle-package.1.html
 	      Package the .gem files required by  your	application  into  the
 	      vendor/cache directory
 
-       [bundle exec(1)][bundle-exec(1)]
+       bundle exec(1) bundle-exec.1.html
 	      Execute a script in the current bundle
 
-       [bundle config(1)][bundle-config(1)]
+       bundle config(1) bundle-config.1.html
 	      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) bundle-add.1.html
 	      Add the named gem to the Gemfile and run bundle install
 
-       [bundle binstubs(1)][bundle-binstubs(1)]
+       bundle binstubs(1) bundle-binstubs.1.html
 	      Generate binstubs for executables in a gem
 
-       [bundle check(1)][bundle-check(1)]
+       bundle check(1) bundle-check.1.html
 	      Determine  whether  the  requirements  for  your application are
 	      installed and available to Bundler
 
-       [bundle show(1)][bundle-show(1)]
+       bundle show(1) bundle-show.1.html
 	      Show the source location of a particular gem in the bundle
 
-       [bundle outdated(1)][bundle-outdated(1)]
+       bundle outdated(1) bundle-outdated.1.html
 	      Show all of the outdated gems in the current bundle
 
        bundle console(1)
 	      Start an IRB session in the current bundle
 
-       [bundle open(1)][bundle-open(1)]
+       bundle open(1) bundle-open.1.html
 	      Open an installed gem in the editor
 
-       [bundle lock(1)][bundle-lock]
+       bundle lock(1) bundle-lock.1.hmtl
 	      Generate a lockfile for your dependencies
 
-       [bundle viz(1)][bundle-viz(1)]
+       bundle viz(1) bundle-viz.1.html
 	      Generate a visual representation of your dependencies
 
-       [bundle init(1)][bundle-init(1)]
+       bundle init(1) bundle-init.1.html
 	      Generate a simple Gemfile, placed in the current directory
 
-       [bundle gem(1)][bundle-gem(1)]
+       bundle gem(1) bundle-gem.1.html
 	      Create a simple gem, suitable for development with Bundler
 
-       [bundle platform(1)][bundle-platform(1)]
+       bundle platform(1) bundle-platform.1.html
 	      Display platform compatibility information
 
-       [bundle clean(1)][bundle-clean(1)]
+       bundle clean(1) bundle-clean.1.html
 	      Clean up unused gems in your Bundler directory
 
-       bundle doctor(1)
+       bundle doctor(1) bundle-doctor.1.html
 	      Display warnings about common problems
 
 PLUGINS
@@ -110,4 +110,4 @@ OBSOLETE
 
 
 
-				   May 2018			     BUNDLE(1)
+				   July 2018			     BUNDLE(1)

data/man/bundle.ronn

@@ -30,20 +30,20 @@ We divide `bundle` subcommands into primary commands and utilities:
 
 ## PRIMARY COMMANDS
 
-* [`bundle install(1)`][bundle-install(1)]:
+* [`bundle install(1)`](bundle-install.1.html):
   Install the gems specified by the `Gemfile` or `Gemfile.lock`
 
-* [`bundle update(1)`][bundle-update(1)]:
+* [`bundle update(1)`](bundle-update.1.html):
   Update dependencies to their latest versions
 
-* [`bundle package(1)`][bundle-package(1)]:
+* [`bundle package(1)`](bundle-package.1.html):
   Package the .gem files required by your application into the
   `vendor/cache` directory
 
-* [`bundle exec(1)`][bundle-exec(1)]:
+* [`bundle exec(1)`](bundle-exec.1.html):
   Execute a script in the current bundle
 
-* [`bundle config(1)`][bundle-config(1)]:
+* [`bundle config(1)`](bundle-config.1.html):
   Specify and read configuration options for Bundler
 
 * `bundle help(1)`:
@@ -51,47 +51,47 @@ We divide `bundle` subcommands into primary commands and utilities:
 
 ## UTILITIES
 
-* [`bundle add(1)`][bundle-add(1)]:
+* [`bundle add(1)`](bundle-add.1.html):
   Add the named gem to the Gemfile and run `bundle install`
 
-* [`bundle binstubs(1)`][bundle-binstubs(1)]:
+* [`bundle binstubs(1)`](bundle-binstubs.1.html):
   Generate binstubs for executables in a gem
 
-* [`bundle check(1)`][bundle-check(1)]:
+* [`bundle check(1)`](bundle-check.1.html):
   Determine whether the requirements for your application are installed
   and available to Bundler
 
-* [`bundle show(1)`][bundle-show(1)]:
+* [`bundle show(1)`](bundle-show.1.html):
   Show the source location of a particular gem in the bundle
 
-* [`bundle outdated(1)`][bundle-outdated(1)]:
+* [`bundle outdated(1)`](bundle-outdated.1.html):
   Show all of the outdated gems in the current bundle
 
 * `bundle console(1)`:
   Start an IRB session in the current bundle
 
-* [`bundle open(1)`][bundle-open(1)]:
+* [`bundle open(1)`](bundle-open.1.html):
   Open an installed gem in the editor
 
-* [`bundle lock(1)`][bundle-lock]:
+* [`bundle lock(1)`](bundle-lock.1.hmtl):
   Generate a lockfile for your dependencies
 
-* [`bundle viz(1)`][bundle-viz(1)]:
+* [`bundle viz(1)`](bundle-viz.1.html):
   Generate a visual representation of your dependencies
 
-* [`bundle init(1)`][bundle-init(1)]:
+* [`bundle init(1)`](bundle-init.1.html):
   Generate a simple `Gemfile`, placed in the current directory
 
-* [`bundle gem(1)`][bundle-gem(1)]:
+* [`bundle gem(1)`](bundle-gem.1.html):
   Create a simple gem, suitable for development with Bundler
 
-* [`bundle platform(1)`][bundle-platform(1)]:
+* [`bundle platform(1)`](bundle-platform.1.html):
   Display platform compatibility information
 
-* [`bundle clean(1)`][bundle-clean(1)]:
+* [`bundle clean(1)`](bundle-clean.1.html):
   Clean up unused gems in your Bundler directory
 
-* `bundle doctor(1)`:
+* [`bundle doctor(1)`](bundle-doctor.1.html):
   Display warnings about common problems
 
 ## PLUGINS

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" "February 2018" "" ""
+.TH "GEMFILE" "5" "July 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(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\.
+Some gem sources require a username and password\. Use bundle config(1) \fIbundle\-config\.1\.html\fR 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][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\.
+All operations involving groups (\fBbundle install\fR \fIbundle\-install\.1\.html\fR, \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\.
@@ -349,6 +349,9 @@ Bundler will search for child dependencies of this gem by first looking in the s
 .P
 Selecting a specific source repository this way also suppresses the ambiguous gem warning described above in \fIGLOBAL SOURCES (#source)\fR\.
 .
+.P
+Using the \fB:source\fR option for an individual gem will also make that source available as a possible global source for any other gems which do not specify explicit sources\. Thus, when adding gems with explicit sources, it is recommended that you also ensure all other gems in the Gemfile are using explicit sources\.
+.
 .SS "GIT"
 If necessary, you can specify that a gem is located at a particular git repository using the \fB:git\fR parameter\. The repository can be accessed via several protocols:
 .
@@ -633,6 +636,9 @@ In the case of the group block form the :optional option can be given to prevent
 .P
 In the case of the \fBgit\fR block form, the \fB:ref\fR, \fB:branch\fR, \fB:tag\fR, and \fB:submodules\fR options may be passed to the \fBgit\fR method, and all gems in the block will inherit those options\.
 .
+.P
+The presence of a \fBsource\fR block in a Gemfile also makes that source available as a possible global source for any other gems which do not specify explicit sources\. Thus, when defining source blocks, it is recommended that you also ensure all other gems in the Gemfile are using explicit sources, either via source blocks or \fB:source\fR directives on individual gems\.
+.
 .SH "INSTALL_IF"
 The \fBinstall_if\fR method allows gems to be installed based on a proc or lambda\. This is especially useful for optional gems that can only be used if certain software is installed or some other conditions are met\.
 .

data/man/gemfile.5.ronn

@@ -35,7 +35,7 @@ this warning, by using the [`:source` option](#SOURCE) or a
 
 ### CREDENTIALS
 
-Some gem sources require a username and password. Use [bundle config(1)][bundle-config(1)] to set
+Some gem sources require a username and password. Use [bundle config(1)](bundle-config.1.html) 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.
@@ -228,7 +228,7 @@ As with groups, you can specify one or more platforms:
     gem "ruby-debug", :platforms => :mri_18
     gem "nokogiri",   :platforms => [:mri_18, :jruby]
 
-All operations involving groups ([`bundle install`][bundle-install(1)], `Bundler.setup`,
+All operations involving groups ([`bundle install`](bundle-install.1.html), `Bundler.setup`,
 `Bundler.require`) behave exactly the same as if any groups not
 matching the current platform were explicitly excluded.
 
@@ -251,6 +251,12 @@ Selecting a specific source repository this way also suppresses the ambiguous
 gem warning described above in
 [GLOBAL SOURCES (#source)](#GLOBAL-SOURCES).
 
+Using the `:source` option for an individual gem will also make that source
+available as a possible global source for any other gems which do not specify
+explicit sources. Thus, when adding gems with explicit sources, it is
+recommended that you also ensure all other gems in the Gemfile are using
+explicit sources.
+
 ### GIT
 
 If necessary, you can specify that a gem is located at a particular
@@ -453,6 +459,13 @@ In the case of the `git` block form, the `:ref`, `:branch`, `:tag`,
 and `:submodules` options may be passed to the `git` method, and
 all gems in the block will inherit those options.
 
+The presence of a `source` block in a Gemfile also makes that source
+available as a possible global source for any other gems which do not specify
+explicit sources. Thus, when defining source blocks, it is
+recommended that you also ensure all other gems in the Gemfile are using
+explicit sources, either via source blocks or `:source` directives on
+individual gems.
+
 ## INSTALL_IF
 
 The `install_if` method allows gems to be installed based on a proc or lambda.

data/man/gemfile.5.txt

@@ -40,9 +40,9 @@ GLOBAL SOURCES
        option or a source block.
 
    CREDENTIALS
-       Some gem sources require a username  and  password.  Use  [bundle  con-
-       fig(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
+       Some gem sources require a username and password. Use bundle  config(1)
+       bundle-config.1.html  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.
 
@@ -286,7 +286,7 @@ GEMS
 
 
 
-       All operations involving groups	([bundle  install][bundle-install(1)],
+       All operations involving groups (bundle install	bundle-install.1.html,
        Bundler.setup,  Bundler.require)  behave  exactly  the  same  as if any
        groups not matching the current platform were explicitly excluded.
 
@@ -312,6 +312,12 @@ GEMS
        Selecting a specific source repository this  way  also  suppresses  the
        ambiguous gem warning described above in GLOBAL SOURCES (#source).
 
+       Using  the  :source  option  for  an individual gem will also make that
+       source available as a possible global source for any other  gems  which
+       do  not	specify explicit sources. Thus, when adding gems with explicit
+       sources, it is recommended that you also ensure all other gems  in  the
+       Gemfile are using explicit sources.
+
    GIT
        If necessary, you can specify that a gem is located at a particular git
        repository using the :git parameter. The repository can be accessed via
@@ -570,9 +576,16 @@ BLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS
        modules	options  may  be passed to the git method, and all gems in the
        block will inherit those options.
 
+       The presence of a source block in a  Gemfile  also  makes  that	source
+       available  as  a possible global source for any other gems which do not
+       specify explicit sources. Thus, when defining source blocks, it is rec-
+       ommended  that  you also ensure all other gems in the Gemfile are using
+       explicit sources, either via source blocks  or  :source	directives  on
+       individual gems.
+
 INSTALL_IF
-       The install_if method allows gems to be installed based on  a  proc  or
-       lambda.	This  is  especially useful for optional gems that can only be
+       The  install_if	method	allows gems to be installed based on a proc or
+       lambda. This is especially useful for optional gems that  can  only  be
        used if certain software is installed or some other conditions are met.
 
 
@@ -584,48 +597,48 @@ INSTALL_IF
 
 
 GEMSPEC
-       The  .gemspec  http://guides.rubygems.org/specification-reference/ file
+       The .gemspec  http://guides.rubygems.org/specification-reference/  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
+       Gemspec attributes include the name, description, and homepage of  your
+       gem.  This is also where you specify the dependencies your gem needs to
        run.
 
        If you wish to use Bundler to help install dependencies for a gem while
-       it is being developed, use the gemspec method to pull in the  dependen-
+       it  is being developed, use the gemspec method to pull in the dependen-
        cies listed in the .gemspec file.
 
        The gemspec method adds any runtime dependencies as gem requirements in
-       the default  group.  It	also  adds  development  dependencies  as  gem
-       requirements  in the development group. Finally, it adds a gem require-
+       the  default  group.  It  also  adds  development  dependencies	as gem
+       requirements in the development group. Finally, it adds a gem  require-
        ment on your project (:path => '.'). In conjunction with Bundler.setup,
        this allows you to require project files in your test code as you would
-       if the project were installed as a gem; you  need  not  manipulate  the
+       if  the	project  were  installed as a gem; you need not manipulate the
        load path manually or require project files via relative paths.
 
        The gemspec method supports optional :path, :glob, :name, and :develop-
        ment_group options, which control where bundler looks for the .gemspec,
-       the  glob  it  uses  to look for the gemspec (defaults to: "{,,/*}.gem-
-       spec"), what named .gemspec it uses (if more than one is present),  and
+       the glob it uses to look for the  gemspec  (defaults  to:  "{,,/*}.gem-
+       spec"),	what named .gemspec it uses (if more than one is present), and
        which group development dependencies are included in.
 
-       When  a	gemspec dependency encounters version conflicts during resolu-
-       tion, the local version under development will always  be  selected  --
-       even  if there are remote versions that better match other requirements
+       When a gemspec dependency encounters version conflicts  during  resolu-
+       tion,  the  local  version under development will always be selected --
+       even if there are remote versions that better match other  requirements
        for the gemspec gem.
 
 SOURCE PRIORITY
-       When attempting to locate a gem to satisfy a gem  requirement,  bundler
+       When  attempting  to locate a gem to satisfy a gem requirement, bundler
        uses the following priority order:
 
        1.  The source explicitly attached to the gem (using :source, :path, or
 	   :git)
 
        2.  For implicit gems (dependencies of explicit gems), any source, git,
-	   or  path repository declared on the parent. This results in bundler
-	   prioritizing the ActiveSupport gem from the	Rails  git  repository
+	   or path repository declared on the parent. This results in  bundler
+	   prioritizing  the  ActiveSupport  gem from the Rails git repository
 	   over ones from rubygems.org
 
-       3.  The	sources  specified  via  global  source  lines, searching each
+       3.  The sources specified  via  global  source  lines,  searching  each
 	   source in your Gemfile from last added to first added.
 
 
@@ -633,4 +646,4 @@ SOURCE PRIORITY
 
 
 
-				 February 2018			    GEMFILE(5)
+				   July 2018			    GEMFILE(5)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bundler
 version: !ruby/object:Gem::Version
-  version: 1.16.2
+  version: 1.16.3
 platform: ruby
 authors:
 - André Arko
@@ -17,7 +17,7 @@ authors:
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-05-16 00:00:00.000000000 Z
+date: 2018-07-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: automatiek
@@ -432,7 +432,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: 1.3.6
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.7.6
+rubygems_version: 2.7.7
 signing_key: 
 specification_version: 4
 summary: The best way to manage your application's dependencies