bundler 2.1.0 → 2.2.0.rc.1

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" "December 2019" "" ""
+.TH "BUNDLE\-VIZ" "1" "July 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\-viz\fR \- Generates a visual dependency graph for your Gemfile

data/man/bundle-viz.1.txt

@@ -1,4 +1,4 @@
-BUNDLE-VIZ(1)							 BUNDLE-VIZ(1)
+BUNDLE-VIZ(1)                                                    BUNDLE-VIZ(1)
 
 
 
@@ -10,30 +10,30 @@ SYNOPSIS
        [--without=GROUP GROUP]
 
 DESCRIPTION
-       viz generates a PNG file of the	current  Gemfile(5)  as  a  dependency
+       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) bun-
-       dle-install.1.html.
+       The  associated  gems  must  also  be  installed  via bundle install(1)
+       bundle-install.1.html.
 
 OPTIONS
        --file, -f
-	      The name to use for the generated file. See --format option
+              The name to use for the generated file. See --format option
 
        --format, -F
-	      This is output format option. Supported format is png, jpg, svg,
-	      dot ...
+              This is output format option. Supported format is png, jpg, svg,
+              dot ...
 
        --requirements, -R
-	      Set to show the version of each required dependency.
+              Set to show the version of each required dependency.
 
        --version, -v
-	      Set to show each gem version.
+              Set to show each gem version.
 
        --without, -W
-	      Exclude gems that are part of the specified named group.
+              Exclude gems that are part of the specified named group.
 
 
 
 
-				 December 2019			 BUNDLE-VIZ(1)
+                                   July 2020                     BUNDLE-VIZ(1)

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" "December 2019" "" ""
+.TH "BUNDLE" "1" "July 2020" "" ""
 .
 .SH "NAME"
 \fBbundle\fR \- Ruby Dependency Management

data/man/bundle.1.txt

@@ -1,4 +1,4 @@
-BUNDLE(1)							     BUNDLE(1)
+BUNDLE(1)                                                            BUNDLE(1)
 
 
 
@@ -9,7 +9,7 @@ SYNOPSIS
        bundle COMMAND [--no-color] [--verbose] [ARGS]
 
 DESCRIPTION
-       Bundler	manages  an application's dependencies through its entire life
+       Bundler  manages  an application's dependencies through its entire life
        across many machines systematically and repeatably.
 
        See the bundler website https://bundler.io for information  on  getting
@@ -17,87 +17,87 @@ DESCRIPTION
 
 OPTIONS
        --no-color
-	      Print all output without color
+              Print all output without color
 
        --retry, -r
-	      Specify the number of times you wish to attempt network commands
+              Specify the number of times you wish to attempt network commands
 
        --verbose, -V
-	      Print out additional logging information
+              Print out additional logging information
 
 BUNDLE COMMANDS
        We divide bundle subcommands into primary commands and utilities:
 
 PRIMARY COMMANDS
        bundle install(1) bundle-install.1.html
-	      Install the gems specified by the Gemfile or Gemfile.lock
+              Install the gems specified by the Gemfile or Gemfile.lock
 
        bundle update(1) bundle-update.1.html
-	      Update dependencies to their latest versions
+              Update dependencies to their latest versions
 
        bundle package(1) bundle-package.1.html
-	      Package  the  .gem  files  required by your application into the
-	      vendor/cache directory
+              Package  the  .gem  files  required by your application into the
+              vendor/cache directory
 
        bundle exec(1) bundle-exec.1.html
-	      Execute a script in the current bundle
+              Execute a script in the current bundle
 
        bundle config(1) bundle-config.1.html
-	      Specify and read configuration options for Bundler
+              Specify and read configuration options for Bundler
 
        bundle help(1)
-	      Display detailed help for each subcommand
+              Display detailed help for each subcommand
 
 UTILITIES
        bundle add(1) bundle-add.1.html
-	      Add the named gem to the Gemfile and run bundle install
+              Add the named gem to the Gemfile and run bundle install
 
        bundle binstubs(1) bundle-binstubs.1.html
-	      Generate binstubs for executables in a gem
+              Generate binstubs for executables in a gem
 
        bundle check(1) bundle-check.1.html
-	      Determine whether the  requirements  for	your  application  are
-	      installed and available to Bundler
+              Determine whether the  requirements  for  your  application  are
+              installed and available to Bundler
 
        bundle show(1) bundle-show.1.html
-	      Show the source location of a particular gem in the bundle
+              Show the source location of a particular gem in the bundle
 
        bundle outdated(1) bundle-outdated.1.html
-	      Show all of the outdated gems in the current bundle
+              Show all of the outdated gems in the current bundle
 
        bundle console(1)
-	      Start an IRB session in the current bundle
+              Start an IRB session in the current bundle
 
        bundle open(1) bundle-open.1.html
-	      Open an installed gem in the editor
+              Open an installed gem in the editor
 
        bundle lock(1) bundle-lock.1.html
-	      Generate a lockfile for your dependencies
+              Generate a lockfile for your dependencies
 
        bundle viz(1) bundle-viz.1.html
-	      Generate a visual representation of your dependencies
+              Generate a visual representation of your dependencies
 
        bundle init(1) bundle-init.1.html
-	      Generate a simple Gemfile, placed in the current directory
+              Generate a simple Gemfile, placed in the current directory
 
        bundle gem(1) bundle-gem.1.html
-	      Create a simple gem, suitable for development with Bundler
+              Create a simple gem, suitable for development with Bundler
 
        bundle platform(1) bundle-platform.1.html
-	      Display platform compatibility information
+              Display platform compatibility information
 
        bundle clean(1) bundle-clean.1.html
-	      Clean up unused gems in your Bundler directory
+              Clean up unused gems in your Bundler directory
 
        bundle doctor(1) bundle-doctor.1.html
-	      Display warnings about common problems
+              Display warnings about common problems
 
        bundle remove(1) bundle-remove.1.html
-	      Removes gems from the Gemfile
+              Removes gems from the Gemfile
 
 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
+       When  running  a  command  that  isn't  listed  in  PRIMARY COMMANDS or
+       UTILITIES, Bundler will try to find an executable on  your  path  named
        bundler-<command>  and  execute it, passing down any extra arguments to
        it.
 
@@ -113,4 +113,4 @@ OBSOLETE
 
 
 
-				 December 2019			     BUNDLE(1)
+                                   July 2020                         BUNDLE(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" "December 2019" "" ""
+.TH "GEMFILE" "5" "July 2020" "" ""
 .
 .SH "NAME"
 \fBGemfile\fR \- A format for describing gem dependencies for Ruby programs

data/man/gemfile.5.txt

@@ -1,4 +1,4 @@
-GEMFILE(5)							    GEMFILE(5)
+GEMFILE(5)                                                          GEMFILE(5)
 
 
 
@@ -9,21 +9,21 @@ SYNOPSIS
        A Gemfile describes the gem dependencies required to execute associated
        Ruby code.
 
-       Place the Gemfile in the root of the directory containing  the  associ-
-       ated  code.  For instance, in a Rails application, place the Gemfile in
-       the same directory as the Rakefile.
+       Place  the  Gemfile  in  the  root  of  the  directory  containing  the
+       associated  code.  For  instance,  in  a  Rails  application, place the
+       Gemfile in the same directory as the Rakefile.
 
 SYNTAX
        A Gemfile is evaluated as Ruby code, in a context which makes available
        a number of methods used to describe the gem requirements.
 
 GLOBAL SOURCES
-       At the top of the Gemfile, add a line for the Rubygems source that con-
-       tains the gems listed in the Gemfile.
+       At  the  top  of  the  Gemfile, add a line for the Rubygems source that
+       contains the gems listed in the Gemfile.
 
 
 
-	   source "https://rubygems.org"
+           source "https://rubygems.org"
 
 
 
@@ -31,24 +31,24 @@ GLOBAL SOURCES
        global  source  lines.  Each  of these sources MUST be a valid Rubygems
        repository.
 
-       Sources are checked for gems  following	the  heuristics  described  in
+       Sources are checked for gems  following  the  heuristics  described  in
        SOURCE  PRIORITY.  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 avail-
-       able. A specific source can be selected for gems that  need  to	use  a
-       non-standard repository, suppressing this warning, by using the :source
-       option or a source block.
+       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
+       :source option or a source block.
 
    CREDENTIALS
        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
+       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.
 
 
 
-	   bundle config gems.example.com user:password
+           bundle config gems.example.com user:password
 
 
 
@@ -57,7 +57,7 @@ GLOBAL SOURCES
 
 
 
-	   source "https://user:password@gems.example.com"
+           source "https://user:password@gems.example.com"
 
 
 
@@ -71,13 +71,13 @@ RUBY
 
    VERSION (required)
        The version of Ruby that your application requires. If your application
-       requires  an  alternate	Ruby  engine, such as JRuby, Rubinius or Truf-
-       fleRuby, this should be the Ruby version that the engine is  compatible
-       with.
+       requires   an  alternate  Ruby  engine,  such  as  JRuby,  Rubinius  or
+       TruffleRuby, this should  be  the  Ruby  version  that  the  engine  is
+       compatible with.
 
 
 
-	   ruby "1.9.3"
+           ruby "1.9.3"
 
 
 
@@ -88,29 +88,29 @@ RUBY
        What exactly is an Engine? - A Ruby engine is an implementation of  the
        Ruby language.
 
-       o   For	background:  the  reference  or original implementation of the
-	   Ruby  programming  language	is  called  Matz's  Ruby   Interpreter
-	   https://en.wikipedia.org/wiki/Ruby_MRI,  or	MRI for short. This is
-	   named after Ruby creator Yukihiro Matsumoto, also  known  as  Matz.
-	   MRI	is also known as CRuby, because it is written in C. MRI is the
-	   most widely used Ruby engine.
+       o   For  background:  the  reference  or original implementation of the
+           Ruby  programming  language  is  called  Matz's  Ruby   Interpreter
+           https://en.wikipedia.org/wiki/Ruby_MRI,  or  MRI for short. This is
+           named after Ruby creator Yukihiro Matsumoto, also  known  as  Matz.
+           MRI  is also known as CRuby, because it is written in C. MRI is the
+           most widely used Ruby engine.
 
        o   Other implementations https://www.ruby-lang.org/en/about/  of  Ruby
-	   exist. Some of the more well-known implementations include Rubinius
-	   https://rubinius.com/, and JRuby http://jruby.org/. Rubinius is  an
-	   alternative	implementation	of  Ruby  written in Ruby. JRuby is an
-	   implementation of Ruby on the JVM, short for Java Virtual Machine.
+           exist. Some of the more well-known implementations include Rubinius
+           https://rubinius.com/, and JRuby http://jruby.org/. Rubinius is  an
+           alternative  implementation  of  Ruby  written in Ruby. JRuby is an
+           implementation of Ruby on the JVM, short for Java Virtual Machine.
 
 
 
    ENGINE VERSION
-       Each application may specify a Ruby engine version. If an  engine  ver-
-       sion  is  specified, an engine must also be specified. If the engine is
-       "ruby" the engine version specified must match the Ruby version.
+       Each application may specify  a  Ruby  engine  version.  If  an  engine
+       version  is  specified, an engine must also be specified. If the engine
+       is "ruby" the engine version specified must match the Ruby version.
 
 
 
-	   ruby "1.8.7", :engine => "jruby", :engine_version => "1.6.7"
+           ruby "1.8.7", :engine => "jruby", :engine_version => "1.6.7"
 
 
 
@@ -119,20 +119,20 @@ RUBY
 
 
 
-	   ruby "2.0.0", :patchlevel => "247"
+           ruby "2.0.0", :patchlevel => "247"
 
 
 
 GEMS
-       Specify gem requirements using the gem method, with the following argu-
-       ments. All parameters are OPTIONAL unless otherwise specified.
+       Specify gem requirements using  the  gem  method,  with  the  following
+       arguments. All parameters are OPTIONAL unless otherwise specified.
 
    NAME (required)
        For each gem requirement, list a single gem line.
 
 
 
-	   gem "nokogiri"
+           gem "nokogiri"
 
 
 
@@ -141,22 +141,22 @@ GEMS
 
 
 
-	   gem "nokogiri", ">= 1.4.2"
-	   gem "RedCloth", ">= 4.1.0", "< 4.2.0"
+           gem "nokogiri", ">= 1.4.2"
+           gem "RedCloth", ">= 4.1.0", "< 4.2.0"
 
 
 
    REQUIRE AS
        Each  gem  MAY specify files that should be used when autorequiring via
        Bundler.require. You may pass an array with multiple files or  true  if
-       file  you  want	required  has same name as gem or false to prevent any
+       file  you  want  required  has same name as gem or false to prevent any
        file from being autorequired.
 
 
 
-	   gem "redis", :require => ["redis/connection/hiredis", "redis"]
-	   gem "webmock", :require => false
-	   gem "byebug", :require => true
+           gem "redis", :require => ["redis/connection/hiredis", "redis"]
+           gem "webmock", :require => false
+           gem "byebug", :require => true
 
 
 
@@ -165,21 +165,21 @@ GEMS
 
 
 
-	   gem "nokogiri"
-	   gem "nokogiri", :require => "nokogiri"
-	   gem "nokogiri", :require => true
+           gem "nokogiri"
+           gem "nokogiri", :require => "nokogiri"
+           gem "nokogiri", :require => true
 
 
 
    GROUPS
-       Each  gem  MAY  specify	membership in one or more groups. Any gem that
+       Each  gem  MAY  specify  membership in one or more groups. Any gem that
        does not specify membership in any  group  is  placed  in  the  default
        group.
 
 
 
-	   gem "rspec", :group => :test
-	   gem "wirble", :groups => [:development, :test]
+           gem "rspec", :group => :test
+           gem "wirble", :groups => [:development, :test]
 
 
 
@@ -188,47 +188,47 @@ GEMS
 
 
 
-	   # setup adds gems to Ruby's load path
-	   Bundler.setup		    # defaults to all groups
-	   require "bundler/setup"	    # same as Bundler.setup
-	   Bundler.setup(:default)	    # only set up the _default_ group
-	   Bundler.setup(:test) 	    # only set up the _test_ group (but `not` _default_)
-	   Bundler.setup(:default, :test)   # set up the _default_ and _test_ groups, but no others
+           # setup adds gems to Ruby's load path
+           Bundler.setup                    # defaults to all groups
+           require "bundler/setup"          # same as Bundler.setup
+           Bundler.setup(:default)          # only set up the _default_ group
+           Bundler.setup(:test)             # only set up the _test_ group (but `not` _default_)
+           Bundler.setup(:default, :test)   # set up the _default_ and _test_ groups, but no others
 
-	   # require requires all of the gems in the specified groups
-	   Bundler.require		    # defaults to the _default_ group
-	   Bundler.require(:default)	    # identical
-	   Bundler.require(:default, :test) # requires the _default_ and _test_ groups
-	   Bundler.require(:test)	    # requires the _test_ group
+           # require requires all of the gems in the specified groups
+           Bundler.require                  # defaults to the _default_ group
+           Bundler.require(:default)        # identical
+           Bundler.require(:default, :test) # requires the _default_ and _test_ groups
+           Bundler.require(:test)           # requires the _test_ group
 
 
 
-       The Bundler CLI allows you to specify a list of groups whose gems  bun-
-       dle install should not install with the without configuration.
+       The Bundler CLI allows you to specify  a  list  of  groups  whose  gems
+       bundle install should not install with the without configuration.
 
-       To  specify  multiple  groups to ignore, specify a list of groups sepa-
-       rated by spaces.
+       To  specify  multiple  groups  to  ignore,  specify  a  list  of groups
+       separated by spaces.
 
 
 
-	   bundle config set without test
-	   bundle config set without development test
+           bundle config set without test
+           bundle config set without development test
 
 
 
        Also, calling Bundler.setup with  no  parameters,  or  calling  require
-       "bundler/setup"	will setup all groups except for the ones you excluded
+       "bundler/setup"  will setup all groups except for the ones you excluded
        via --without (since they are not available).
 
        Note that on bundle install, bundler downloads and evaluates all  gems,
        in  order to create a single canonical list of all of the required gems
-       and their dependencies. This means that you cannot list different  ver-
-       sions  of  the  same  gems  in  different groups. For more details, see
+       and their dependencies. This  means  that  you  cannot  list  different
+       versions  of  the  same gems in different groups. For more details, see
        Understanding Bundler https://bundler.io/rationale.html.
 
    PLATFORMS
-       If a gem should only be used in a particular platform or set  of  plat-
-       forms,  you  can  specify  them. Platforms are essentially identical to
+       If a gem should only be  used  in  a  particular  platform  or  set  of
+       platforms, you can specify them. Platforms are essentially identical to
        groups, except that you do not need to use the  --without  install-time
        flag to exclude groups of gems for other platforms.
 
@@ -241,27 +241,27 @@ GEMS
        mingw  Windows 32 bit 'mingw32' platform (aka RubyInstaller)
 
        x64_mingw
-	      Windows 64 bit 'mingw32' platform (aka RubyInstaller x64)
+              Windows 64 bit 'mingw32' platform (aka RubyInstaller x64)
 
        rbx    Rubinius
 
        jruby  JRuby
 
        truffleruby
-	      TruffleRuby
+              TruffleRuby
 
        mswin  Windows
 
-       You  can  restrict  further  by	platform and version for all platforms
+       You  can  restrict  further  by  platform and version for all platforms
        except for rbx, jruby, truffleruby and mswin.
 
-       To specify a version in addition to a platform, append the version num-
-       ber without the delimiter to the platform. For example, to specify that
-       a gem should only be used on platforms with Ruby 2.3, use:
+       To specify a version in addition to  a  platform,  append  the  version
+       number  without  the delimiter to the platform. For example, to specify
+       that a gem should only be used on platforms with Ruby 2.3, use:
 
 
 
-	   ruby_23
+           ruby_23
 
 
 
@@ -274,19 +274,19 @@ GEMS
        mingw  1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
 
        x64_mingw
-	      2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
+              2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6
 
        As with groups, you can specify one or more platforms:
 
 
 
-	   gem "weakling",   :platforms => :jruby
-	   gem "ruby-debug", :platforms => :mri_18
-	   gem "nokogiri",   :platforms => [:mri_18, :jruby]
+           gem "weakling",   :platforms => :jruby
+           gem "ruby-debug", :platforms => :mri_18
+           gem "nokogiri",   :platforms => [:mri_18, :jruby]
 
 
 
-       All operations involving groups (bundle install	bundle-install.1.html,
+       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.
 
@@ -296,7 +296,7 @@ GEMS
 
 
 
-	   gem "some_internal_gem", :source => "https://gems.example.com"
+           gem "some_internal_gem", :source => "https://gems.example.com"
 
 
 
@@ -314,7 +314,7 @@ GEMS
 
        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
+       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.
 
@@ -324,7 +324,7 @@ GEMS
        several protocols:
 
        HTTP(S)
-	      gem "rails", :git => "https://github.com/rails/rails.git"
+              gem "rails", :git => "https://github.com/rails/rails.git"
 
        SSH    gem "rails", :git => "git@github.com:rails/rails.git"
 
@@ -333,95 +333,95 @@ GEMS
        If using SSH, the user that you use to run bundle install MUST have the
        appropriate keys available in their $HOME/.ssh.
 
-       NOTE: http:// and git:// URLs should be avoided	if  at	all  possible.
+       NOTE: http:// and git:// URLs should be avoided  if  at  all  possible.
        These  protocols  are  unauthenticated, so a man-in-the-middle attacker
        can deliver malicious code and compromise your system.  HTTPS  and  SSH
        are strongly preferred.
 
-       The  group,  platforms,	and  require  options are available and behave
+       The  group,  platforms,  and  require  options are available and behave
        exactly the same as they would for a normal gem.
 
-       A git repository SHOULD have at least one file,	at  the  root  of  the
+       A git repository SHOULD have at least one file,  at  the  root  of  the
        directory  containing  the  gem, with the extension .gemspec. This file
        MUST contain a valid gem specification, as expected by  the  gem  build
        command.
 
        If  a  git repository does not have a .gemspec, bundler will attempt to
        create one, but it will not contain any dependencies, executables, or C
-       extension  compilation  instructions. As a result, it may fail to prop-
-       erly integrate into your application.
+       extension  compilation  instructions.  As  a  result,  it  may  fail to
+       properly integrate into your application.
 
        If a git repository does have a .gemspec for the gem  you  attached  it
        to,  a version specifier, if provided, means that the git repository is
-       only valid if the .gemspec specifies a  version	matching  the  version
+       only valid if the .gemspec specifies a  version  matching  the  version
        specifier. If not, bundler will print a warning.
 
 
 
-	   gem "rails", "2.3.8", :git => "https://github.com/rails/rails.git"
-	   # bundle install will fail, because the .gemspec in the rails
-	   # repository's master branch specifies version 3.0.0
+           gem "rails", "2.3.8", :git => "https://github.com/rails/rails.git"
+           # bundle install will fail, because the .gemspec in the rails
+           # repository's master branch specifies version 3.0.0
 
 
 
        If  a  git repository does not have a .gemspec for the gem you attached
-       it to, a version specifier MUST be provided. Bundler will use this ver-
-       sion in the simple .gemspec it creates.
+       it to, a version specifier MUST be  provided.  Bundler  will  use  this
+       version in the simple .gemspec it creates.
 
        Git repositories support a number of additional options.
 
        branch, tag, and ref
-	      You  MUST only specify at most one of these options. The default
-	      is :branch => "master". For example:
+              You  MUST only specify at most one of these options. The default
+              is :branch => "master". For example:
 
-	      gem  "rails",  :git   =>	 "https://github.com/rails/rails.git",
-	      :branch => "5-0-stable"
+              gem  "rails",  :git   =>   "https://github.com/rails/rails.git",
+              :branch => "5-0-stable"
 
-	      gem  "rails", :git => "https://github.com/rails/rails.git", :tag
-	      => "v5.0.0"
+              gem  "rails", :git => "https://github.com/rails/rails.git", :tag
+              => "v5.0.0"
 
-	      gem "rails", :git => "https://github.com/rails/rails.git",  :ref
-	      => "4aded"
+              gem "rails", :git => "https://github.com/rails/rails.git",  :ref
+              => "4aded"
 
        submodules
-	      For	   reference,	       a	 git	     submodule
-	      https://git-scm.com/book/en/v2/Git-Tools-Submodules   lets   you
-	      have  another  git repository within a subfolder of your reposi-
-	      tory. Specify :submodules => true to cause bundler to expand any
-	      submodules included in the git repository
+              For          reference,          a         git         submodule
+              https://git-scm.com/book/en/v2/Git-Tools-Submodules   lets   you
+              have   another   git  repository  within  a  subfolder  of  your
+              repository. Specify :submodules =>  true  to  cause  bundler  to
+              expand any submodules included in the git repository
 
-       If  a  git repository contains multiple .gemspecs, each .gemspec repre-
-       sents a gem located at the same place in the file system as  the  .gem-
-       spec.
+       If   a  git  repository  contains  multiple  .gemspecs,  each  .gemspec
+       represents a gem located at the same place in the file  system  as  the
+       .gemspec.
 
 
 
-	   |~rails		     [git root]
-	   | |-rails.gemspec	     [rails gem located here]
-	   |~actionpack
-	   | |-actionpack.gemspec    [actionpack gem located here]
-	   |~activesupport
-	   | |-activesupport.gemspec [activesupport gem located here]
-	   |...
+           |~rails                   [git root]
+           | |-rails.gemspec         [rails gem located here]
+           |~actionpack
+           | |-actionpack.gemspec    [actionpack gem located here]
+           |~activesupport
+           | |-activesupport.gemspec [activesupport gem located here]
+           |...
 
 
 
        To  install  a  gem located in a git repository, bundler changes to the
        directory containing the gemspec, runs gem build name.gemspec and  then
        installs the resulting gem. The gem build command, which comes standard
-       with Rubygems, evaluates the .gemspec in the context of	the  directory
+       with Rubygems, evaluates the .gemspec in the context of  the  directory
        in which it is located.
 
    GIT SOURCE
        A  custom  git source can be defined via the git_source method. Provide
-       the source's name as an argument, and a block which receives  a	single
-       argument  and  interpolates  it	into  a string to return the full repo
+       the source's name as an argument, and a block which receives  a  single
+       argument  and  interpolates  it  into  a string to return the full repo
        address:
 
 
 
-	   git_source(:stash){ |repo_name| "https://stash.corp.acme.pl/#{repo_name}.git" }
-	   gem 'rails', :stash => 'forks/rails'
+           git_source(:stash){ |repo_name| "https://stash.corp.acme.pl/#{repo_name}.git" }
+           gem 'rails', :stash => 'forks/rails'
 
 
 
@@ -429,25 +429,25 @@ GEMS
 
 
 
-	   gem "rails", :stash => "forks/rails", :branch => "branch_name"
+           gem "rails", :stash => "forks/rails", :branch => "branch_name"
 
 
 
    GITHUB
-       NOTE: This shorthand should be avoided until Bundler 2.0, since it cur-
-       rently expands to an insecure git:// URL. This allows a man-in-the-mid-
-       dle attacker to compromise your system.
+       NOTE: This shorthand should be avoided  until  Bundler  2.0,  since  it
+       currently   expands   to   an   insecure  git://  URL.  This  allows  a
+       man-in-the-middle attacker to compromise your system.
 
-       If the git repository you want to use is hosted on GitHub and  is  pub-
-       lic,  you  can use the :github shorthand to specify the github username
-       and repository name (without  the  trailing  ".git"),  separated  by  a
-       slash.  If  both the username and repository name are the same, you can
-       omit one.
+       If the git repository you want to  use  is  hosted  on  GitHub  and  is
+       public,  you  can  use  the  :github  shorthand  to  specify the github
+       username and repository name (without the trailing  ".git"),  separated
+       by  a slash. If both the username and repository name are the same, you
+       can omit one.
 
 
 
-	   gem "rails", :github => "rails/rails"
-	   gem "rails", :github => "rails"
+           gem "rails", :github => "rails/rails"
+           gem "rails", :github => "rails"
 
 
 
@@ -455,7 +455,7 @@ GEMS
 
 
 
-	   gem "rails", :git => "git://github.com/rails/rails.git"
+           gem "rails", :git => "git://github.com/rails/rails.git"
 
 
 
@@ -469,7 +469,7 @@ GEMS
 
 
 
-	   gem "the_hatch", :gist => "4815162342"
+           gem "the_hatch", :gist => "4815162342"
 
 
 
@@ -477,7 +477,7 @@ GEMS
 
 
 
-	   gem "the_hatch", :git => "https://gist.github.com/4815162342.git"
+           gem "the_hatch", :git => "https://gist.github.com/4815162342.git"
 
 
 
@@ -485,16 +485,16 @@ GEMS
        :branch named argument.
 
    BITBUCKET
-       If the git repository you want to use is hosted	on  Bitbucket  and  is
-       public,	you  can use the :bitbucket shorthand to specify the bitbucket
+       If the git repository you want to use is hosted  on  Bitbucket  and  is
+       public,  you  can use the :bitbucket shorthand to specify the bitbucket
        username and repository name (without the trailing  ".git"),  separated
        by  a slash. If both the username and repository name are the same, you
        can omit one.
 
 
 
-	   gem "rails", :bitbucket => "rails/rails"
-	   gem "rails", :bitbucket => "rails"
+           gem "rails", :bitbucket => "rails/rails"
+           gem "rails", :bitbucket => "rails"
 
 
 
@@ -502,19 +502,19 @@ GEMS
 
 
 
-	   gem "rails", :git => "https://rails@bitbucket.org/rails/rails.git"
+           gem "rails", :git => "https://rails@bitbucket.org/rails/rails.git"
 
 
 
-       Since the bitbucket  method  is	a  specialization  of  git_source,  it
+       Since the bitbucket  method  is  a  specialization  of  git_source,  it
        accepts a :branch named argument.
 
    PATH
        You  can  specify that a gem is located in a particular location on the
-       file system. Relative paths are resolved relative to the directory con-
-       taining the Gemfile.
+       file system. Relative paths are  resolved  relative  to  the  directory
+       containing the Gemfile.
 
-       Similar	to the semantics of the :git option, the :path option requires
+       Similar  to the semantics of the :git option, the :path option requires
        that the directory in question either contains a .gemspec for the  gem,
        or that you specify an explicit version that bundler should use.
 
@@ -523,20 +523,21 @@ GEMS
 
 
 
-	   gem "rails", :path => "vendor/rails"
+           gem "rails", :path => "vendor/rails"
 
 
 
-       If you would like to use multiple local gems directly from the filesys-
-       tem,  you can set a global path option to the path containing the gem's
-       files. This will automatically load gemspec files from subdirectories.
+       If you would  like  to  use  multiple  local  gems  directly  from  the
+       filesystem, you can set a global path option to the path containing the
+       gem's  files.  This  will  automatically  load   gemspec   files   from
+       subdirectories.
 
 
 
-	   path 'components' do
-	     gem 'admin_ui'
-	     gem 'public_ui'
-	   end
+           path 'components' do
+             gem 'admin_ui'
+             gem 'public_ui'
+           end
 
 
 
@@ -546,104 +547,105 @@ BLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS
 
 
 
-	   source "https://gems.example.com" do
-	     gem "some_internal_gem"
-	     gem "another_internal_gem"
-	   end
+           source "https://gems.example.com" do
+             gem "some_internal_gem"
+             gem "another_internal_gem"
+           end
 
-	   git "https://github.com/rails/rails.git" do
-	     gem "activesupport"
-	     gem "actionpack"
-	   end
+           git "https://github.com/rails/rails.git" do
+             gem "activesupport"
+             gem "actionpack"
+           end
 
-	   platforms :ruby do
-	     gem "ruby-debug"
-	     gem "sqlite3"
-	   end
+           platforms :ruby do
+             gem "ruby-debug"
+             gem "sqlite3"
+           end
 
-	   group :development, :optional => true do
-	     gem "wirble"
-	     gem "faker"
-	   end
+           group :development, :optional => true do
+             gem "wirble"
+             gem "faker"
+           end
 
 
 
-       In  the	case of the group block form the :optional option can be given
-       to prevent a group from being installed unless  listed  in  the	--with
+       In the case of the group block form the :optional option can  be  given
+       to  prevent  a  group  from being installed unless listed in the --with
        option given to the bundle install command.
 
-       In  the	case of the git block form, the :ref, :branch, :tag, and :sub-
-       modules options may be passed to the git method, and all  gems  in  the
-       block will inherit those options.
+       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 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.
+       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.	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.
 
 
 
-	   install_if -> { RUBY_PLATFORM =~ /darwin/ } do
-	     gem "pasteboard"
-	   end
+           install_if -> { RUBY_PLATFORM =~ /darwin/ } do
+             gem "pasteboard"
+           end
 
 
 
 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-
-       cies listed in the .gemspec file.
+       it  is  being  developed,  use  the  gemspec  method  to  pull  in  the
+       dependencies 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-
-       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
-       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
-       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
-       for the gemspec gem.
+       the default  group.  It  also  adds  development  dependencies  as  gem
+       requirements   in  the  development  group.  Finally,  it  adds  a  gem
+       requirement 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 load path manually or require project files via relative
+       paths.
+
+       The  gemspec  method  supports  optional  :path,  :glob,   :name,   and
+       :development_group  options,  which control where bundler looks for the
+       .gemspec, the glob it uses  to  look  for  the  gemspec  (defaults  to:
+       "{,,/*}.gemspec"),  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
+       resolution, 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
        uses the following priority order:
 
        1.  The source explicitly attached to the gem (using :source, :path, or
-	   :git)
+           :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
-	   over ones from rubygems.org
+           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
-	   source in your Gemfile from last added to first added.
+           source in your Gemfile from last added to first added.
 
 
 
 
 
 
-				 December 2019			    GEMFILE(5)
+                                   July 2020                        GEMFILE(5)