bundler 1.16.4 → 1.16.5

data/man/bundle-init.1.txt

@@ -31,4 +31,4 @@ SEE ALSO
 
 
 
-				  August 2018			BUNDLE-INIT(1)
+				September 2018			BUNDLE-INIT(1)

data/man/bundle-inject.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INJECT" "1" "August 2018" "" ""
+.TH "BUNDLE\-INJECT" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile

data/man/bundle-inject.1.txt

@@ -29,4 +29,4 @@ DESCRIPTION
 
 
 
-				  August 2018		      BUNDLE-INJECT(1)
+				September 2018		      BUNDLE-INJECT(1)

data/man/bundle-install.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INSTALL" "1" "August 2018" "" ""
+.TH "BUNDLE\-INSTALL" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-install\fR \- Install the dependencies specified in your Gemfile

data/man/bundle-install.1.txt

@@ -382,4 +382,4 @@ SEE ALSO
 
 
 
-				  August 2018		     BUNDLE-INSTALL(1)
+				September 2018		     BUNDLE-INSTALL(1)

data/man/bundle-list.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LIST" "1" "August 2018" "" ""
+.TH "BUNDLE\-LIST" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-list\fR \- List all the gems in the bundle

data/man/bundle-list.1.txt

@@ -18,4 +18,4 @@ OPTIONS
 
 
 
-				  August 2018			BUNDLE-LIST(1)
+				September 2018			BUNDLE-LIST(1)

data/man/bundle-lock.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-LOCK" "1" "August 2018" "" ""
+.TH "BUNDLE\-LOCK" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-lock\fR \- Creates / Updates a lockfile without installing

data/man/bundle-lock.1.txt

@@ -90,4 +90,4 @@ PATCH LEVEL OPTIONS
 
 
 
-				  August 2018			BUNDLE-LOCK(1)
+				September 2018			BUNDLE-LOCK(1)

data/man/bundle-open.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OPEN" "1" "August 2018" "" ""
+.TH "BUNDLE\-OPEN" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-open\fR \- Opens the source directory for a gem in your bundle

data/man/bundle-open.1.txt

@@ -26,4 +26,4 @@ DESCRIPTION
 
 
 
-				  August 2018			BUNDLE-OPEN(1)
+				September 2018			BUNDLE-OPEN(1)

data/man/bundle-outdated.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-OUTDATED" "1" "August 2018" "" ""
+.TH "BUNDLE\-OUTDATED" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-outdated\fR \- List installed gems with newer versions available

data/man/bundle-outdated.1.txt

@@ -124,4 +124,4 @@ FILTERING OUTPUT
 
 
 
-				  August 2018		    BUNDLE-OUTDATED(1)
+				September 2018		    BUNDLE-OUTDATED(1)

data/man/bundle-package.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PACKAGE" "1" "August 2018" "" ""
+.TH "BUNDLE\-PACKAGE" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-package\fR \- Package your needed \fB\.gem\fR files into your application

data/man/bundle-package.1.txt

@@ -76,4 +76,4 @@ REMOTE FETCHING
 
 
 
-				  August 2018		     BUNDLE-PACKAGE(1)
+				September 2018		     BUNDLE-PACKAGE(1)

data/man/bundle-platform.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PLATFORM" "1" "August 2018" "" ""
+.TH "BUNDLE\-PLATFORM" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-platform\fR \- Displays platform compatibility information

data/man/bundle-platform.1.txt

@@ -54,4 +54,4 @@ OPTIONS
 
 
 
-				  August 2018		    BUNDLE-PLATFORM(1)
+				September 2018		    BUNDLE-PLATFORM(1)

data/man/bundle-pristine.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-PRISTINE" "1" "August 2018" "" ""
+.TH "BUNDLE\-PRISTINE" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-pristine\fR \- Restores installed gems to their pristine condition

data/man/bundle-pristine.1.txt

@@ -41,4 +41,4 @@ DESCRIPTION
 
 
 
-				  August 2018		    BUNDLE-PRISTINE(1)
+				September 2018		    BUNDLE-PRISTINE(1)

data/man/bundle-show.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-SHOW" "1" "August 2018" "" ""
+.TH "BUNDLE\-SHOW" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-show\fR \- Shows all the gems in your bundle, or the path to a gem

data/man/bundle-show.1.txt

@@ -24,4 +24,4 @@ OPTIONS
 
 
 
-				  August 2018			BUNDLE-SHOW(1)
+				September 2018			BUNDLE-SHOW(1)

data/man/bundle-update.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-UPDATE" "1" "August 2018" "" ""
+.TH "BUNDLE\-UPDATE" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-update\fR \- Update your gems to the latest available versions

data/man/bundle-update.1.txt

@@ -385,4 +385,4 @@ RECOMMENDED WORKFLOW
 
 
 
-				  August 2018		      BUNDLE-UPDATE(1)
+				September 2018		      BUNDLE-UPDATE(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" "August 2018" "" ""
+.TH "BUNDLE\-VIZ" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-viz\fR \- Generates a visual dependency graph for your Gemfile

data/man/bundle-viz.1.txt

@@ -36,4 +36,4 @@ OPTIONS
 
 
 
-				  August 2018			 BUNDLE-VIZ(1)
+				September 2018			 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" "August 2018" "" ""
+.TH "BUNDLE" "1" "September 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\fR \- Ruby Dependency Management

data/man/bundle.1.txt

@@ -110,4 +110,4 @@ OBSOLETE
 
 
 
-				  August 2018			     BUNDLE(1)
+				September 2018			     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" "August 2018" "" ""
+.TH "GEMFILE" "5" "September 2018" "" ""
 .
 .SH "NAME"
 \fBGemfile\fR \- A format for describing gem dependencies for Ruby programs
@@ -67,7 +67,7 @@ Credentials in the source URL will take precedence over credentials set using \f
 If your application requires a specific Ruby version or engine, specify your requirements using the \fBruby\fR method, with the following arguments\. All parameters are \fBOPTIONAL\fR unless otherwise specified\.
 .
 .SS "VERSION (required)"
-The version of Ruby that your application requires\. If your application requires an alternate Ruby engine, such as JRuby or Rubinius, this should be the Ruby version that the engine is compatible with\.
+The version of Ruby that your application requires\. If your application requires an alternate Ruby engine, such as JRuby, Rubinius or TruffleRuby, this should be the Ruby version that the engine is compatible with\.
 .
 .IP "" 4
 .
@@ -248,11 +248,11 @@ There are a number of \fBGemfile\fR platforms:
 .
 .TP
 \fBruby\fR
-C Ruby (MRI) or Rubinius, but \fBNOT\fR Windows
+C Ruby (MRI), Rubinius or TruffleRuby, but \fBNOT\fR Windows
 .
 .TP
 \fBmri\fR
-Same as \fIruby\fR, but not Rubinius
+Same as \fIruby\fR, but only C Ruby (MRI)
 .
 .TP
 \fBmingw\fR
@@ -264,18 +264,22 @@ Windows 64 bit \'mingw32\' platform (aka RubyInstaller x64)
 .
 .TP
 \fBrbx\fR
-Same as \fIruby\fR, but only Rubinius (not MRI)
+Rubinius
 .
 .TP
 \fBjruby\fR
 JRuby
 .
 .TP
+\fBtruffleruby\fR
+TruffleRuby
+.
+.TP
 \fBmswin\fR
 Windows
 .
 .P
-You can restrict further by platform and version for all platforms \fIexcept\fR for \fBrbx\fR, \fBjruby\fR, and \fBmswin\fR\.
+You can restrict further by platform and version for all platforms \fIexcept\fR for \fBrbx\fR, \fBjruby\fR, \fBtruffleruby\fR and \fBmswin\fR\.
 .
 .P
 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:

data/man/gemfile.5.ronn

@@ -59,8 +59,8 @@ All parameters are `OPTIONAL` unless otherwise specified.
 ### VERSION (required)
 
 The version of Ruby that your application requires. If your application
-requires an alternate Ruby engine, such as JRuby or Rubinius, 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"
 
@@ -188,22 +188,24 @@ platforms.
 There are a number of `Gemfile` platforms:
 
   * `ruby`:
-    C Ruby (MRI) or Rubinius, but `NOT` Windows
+    C Ruby (MRI), Rubinius or TruffleRuby, but `NOT` Windows
   * `mri`:
-    Same as _ruby_, but not Rubinius
+    Same as _ruby_, but only C Ruby (MRI)
   * `mingw`:
     Windows 32 bit 'mingw32' platform (aka RubyInstaller)
   * `x64_mingw`:
     Windows 64 bit 'mingw32' platform (aka RubyInstaller x64)
   * `rbx`:
-    Same as _ruby_, but only Rubinius (not MRI)
+    Rubinius
   * `jruby`:
     JRuby
+  * `truffleruby`:
+    TruffleRuby
   * `mswin`:
     Windows
 
 You can restrict further by platform and version for all platforms *except* for
-`rbx`, `jruby`, and `mswin`.
+`rbx`, `jruby`, `truffleruby` and `mswin`.
 
 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

data/man/gemfile.5.txt

@@ -71,8 +71,9 @@ RUBY
 
    VERSION (required)
        The version of Ruby that your application requires. If your application
-       requires  an  alternate	Ruby  engine,  such as JRuby or Rubinius, this
-       should be the Ruby version that the engine is compatible with.
+       requires  an  alternate	Ruby  engine, such as JRuby, Rubinius or Truf-
+       fleRuby, this should be the Ruby version that the engine is  compatible
+       with.
 
 
 
@@ -81,30 +82,30 @@ RUBY
 
 
    ENGINE
-       Each application may specify a Ruby engine. If an engine is  specified,
+       Each  application may specify a Ruby engine. If an engine is specified,
        an engine version must also be specified.
 
-       What  exactly is an Engine? - A Ruby engine is an implementation of the
+       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
+       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
+       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.
+	   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
+       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.
 
 
@@ -146,9 +147,9 @@ GEMS
 
 
    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
+       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 from being autorequired.
 
 
@@ -159,7 +160,7 @@ GEMS
 
 
 
-       The argument defaults to the name of the gem. For  example,  these  are
+       The  argument  defaults	to the name of the gem. For example, these are
        identical:
 
 
@@ -171,8 +172,8 @@ GEMS
 
 
    GROUPS
-       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
+       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.
 
 
@@ -182,7 +183,7 @@ GEMS
 
 
 
-       The  Bundler  runtime  allows  its  two main methods, Bundler.setup and
+       The Bundler runtime allows its  two  main  methods,  Bundler.setup  and
        Bundler.require, to limit their impact to particular groups.
 
 
@@ -202,9 +203,9 @@ GEMS
 
 
 
-       The Bundler CLI allows you to specify a list of groups whose gems  bun-
-       dle  install  should  not install with the --without option. To specify
-       multiple groups to ignore, specify a list of groups separated  by  spa-
+       The  Bundler CLI allows you to specify a list of groups whose gems bun-
+       dle install should not install with the --without  option.  To  specify
+       multiple  groups  to ignore, specify a list of groups separated by spa-
        ces.
 
 
@@ -216,44 +217,47 @@ GEMS
 
        After running bundle install --without test, bundler will remember that
        you excluded the test group in the last installation. The next time you
-       run  bundle  install, without any --without option, bundler will recall
+       run bundle install, without any --without option, bundler  will	recall
        it.
 
-       Also, calling Bundler.setup with  no  parameters,  or  calling  require
-       "bundler/setup"	will setup all groups except for the ones you excluded
+       Also,  calling  Bundler.setup  with  no	parameters, or calling require
+       "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
+       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
        Understanding Bundler http://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
-       groups, except that you do not need to use the  --without  install-time
+       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
+       groups,	except	that you do not need to use the --without install-time
        flag to exclude groups of gems for other platforms.
 
        There are a number of Gemfile platforms:
 
-       ruby   C Ruby (MRI) or Rubinius, but NOT Windows
+       ruby   C Ruby (MRI), Rubinius or TruffleRuby, but NOT Windows
 
-       mri    Same as ruby, but not Rubinius
+       mri    Same as ruby, but only C Ruby (MRI)
 
        mingw  Windows 32 bit 'mingw32' platform (aka RubyInstaller)
 
        x64_mingw
 	      Windows 64 bit 'mingw32' platform (aka RubyInstaller x64)
 
-       rbx    Same as ruby, but only Rubinius (not MRI)
+       rbx    Rubinius
 
        jruby  JRuby
 
+       truffleruby
+	      TruffleRuby
+
        mswin  Windows
 
-       You  can  restrict  further  by	platform and version for all platforms
-       except for rbx, jruby, and mswin.
+       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
@@ -286,12 +290,12 @@ GEMS
 
 
 
-       All operations involving groups (bundle install	bundle-install.1.html,
-       Bundler.setup,  Bundler.require)  behave  exactly  the  same  as if any
+       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.
 
    SOURCE
-       You can select an alternate Rubygems repository for  a  gem  using  the
+       You  can  select  an  alternate Rubygems repository for a gem using the
        ':source' option.
 
 
@@ -300,22 +304,22 @@ GEMS
 
 
 
-       This  forces  the  gem  to  be  loaded from this source and ignores any
-       global sources declared at the top level of the file. If the  gem  does
+       This forces the gem to be loaded  from  this  source  and  ignores  any
+       global  sources	declared at the top level of the file. If the gem does
        not exist in this source, it will not be installed.
 
        Bundler will search for child dependencies of this gem by first looking
        in the source selected for the parent, but if they are not found there,
-       it  will  fall  back  on global sources using the ordering described in
+       it will fall back on global sources using  the  ordering  described  in
        SOURCE PRIORITY.
 
-       Selecting a specific source repository this  way  also  suppresses  the
+       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
+       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
@@ -333,27 +337,27 @@ 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.
-       These  protocols  are  unauthenticated, so a man-in-the-middle attacker
-       can deliver malicious code and compromise your system.  HTTPS  and  SSH
+       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
-       directory  containing  the  gem, with the extension .gemspec. This file
-       MUST contain a valid gem specification, as expected by  the  gem  build
+       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
+       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-
+       extension compilation instructions. As a result, it may fail  to  prop-
        erly 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
+       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
        specifier. If not, bundler will print a warning.
 
 
@@ -364,19 +368,19 @@ GEMS
 
 
 
-       If  a  git repository does not have a .gemspec for the gem you attached
+       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.
 
        Git repositories support a number of additional options.
 
        branch, tag, and ref
-	      You  MUST only specify at most one of these options. The default
+	      You MUST only specify at most one of these options. The  default
 	      is :branch => "master"
 
        For example:
 
-	      git "https://github.com/rails/rails.git", :branch  =>  "5-0-sta-
+	      git  "https://github.com/rails/rails.git",  :branch => "5-0-sta-
 	      ble" do
 
 	      git "https://github.com/rails/rails.git", :tag => "v5.0.0" do
@@ -384,14 +388,14 @@ GEMS
 	      git "https://github.com/rails/rails.git", :ref => "4aded" do
 
        submodules
-	      For	   reference,	       a	 git	     submodule
+	      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-
+	      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
 
-       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-
+       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.
 
 
@@ -406,16 +410,16 @@ GEMS
 
 
 
-       To  install  a  gem located in a git repository, bundler changes to the
-       directory containing the gemspec, runs gem build name.gemspec and  then
+       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
+       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
        address:
 
 
@@ -438,10 +442,10 @@ GEMS
        rently expands to an insecure git:// URL. This allows a man-in-the-mid-
        dle 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
+       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.
 
 
@@ -464,7 +468,7 @@ GEMS
 
    GIST
        If the git repository you want to use is hosted as a Github Gist and is
-       public, you can use the :gist shorthand to specify the gist  identifier
+       public,	you can use the :gist shorthand to specify the gist identifier
        (without the trailing ".git").
 
 
@@ -481,14 +485,14 @@ GEMS
 
 
 
-       Since  the  gist method is a specialization of git_source, it accepts a
+       Since the gist method is a specialization of git_source, it  accepts  a
        :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
-       username and repository name (without the trailing  ".git"),  separated
-       by  a slash. If both the username and repository name are the same, you
+       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.
 
 
@@ -506,19 +510,19 @@ GEMS
 
 
 
-       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
+       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.
 
-       Similar	to the semantics of the :git option, the :path option requires
-       that the directory in question either contains a .gemspec for the  gem,
+       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.
 
-       Unlike  :git,  bundler does not compile C extensions for gems specified
+       Unlike :git, bundler does not compile C extensions for  gems  specified
        as paths.
 
 
@@ -528,8 +532,8 @@ GEMS
 
 
        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.
+       tem, you can set a global path option to the path containing the  gem's
+       files.  This will automatically load gemspec files from subdirectories.
 
 
 
@@ -568,24 +572,24 @@ BLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS
 
 
 
-       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
+       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.
 
-       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
+       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
+       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.
 
 
@@ -597,48 +601,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.
 
 
@@ -646,4 +650,4 @@ SOURCE PRIORITY
 
 
 
-				  August 2018			    GEMFILE(5)
+				September 2018			    GEMFILE(5)