bundler 1.15.1 → 1.17.3

data/man/gemfile.5.txt

@@ -2,24 +2,24 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-1mNAME0m
-       1mGemfile 22m- A format for describing gem dependencies for Ruby programs
+NAME
+       Gemfile - A format for describing gem dependencies for Ruby programs
 
-1mSYNOPSIS0m
-       A 1mGemfile 22mdescribes the gem dependencies required to execute associated
+SYNOPSIS
+       A Gemfile describes the gem dependencies required to execute associated
        Ruby code.
 
-       Place the 1mGemfile 22min the root of the directory containing  the  associ-
-       ated  code.  For instance, in a Rails application, place the 1mGemfile 22min
-       the same directory as the 1mRakefile22m.
+       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.
 
-1mSYNTAX0m
-       A 1mGemfile 22mis evaluated as Ruby code, in a context which makes available
+SYNTAX
+       A Gemfile is evaluated as Ruby code, in a context which makes available
        a number of methods used to describe the gem requirements.
 
-1mGLOBAL SOURCES0m
-       At the top of the 1mGemfile22m, add a line for the 1mRubygems 22msource that con-
-       tains the gems listed in the 1mGemfile22m.
+GLOBAL SOURCES
+       At the top of the Gemfile, add a line for the Rubygems source that con-
+       tains the gems listed in the Gemfile.
 
 
 
@@ -28,20 +28,20 @@ GEMFILE(5)							    GEMFILE(5)
 
 
        It is possible, but not recommended as of Bundler 1.7, to add  multiple
-       global  1msource  22mlines.  Each  of these 1msource22ms 1mMUST 22mbe a valid Rubygems
+       global  source  lines.  Each  of these sources MUST be a valid Rubygems
        repository.
 
        Sources are checked for gems  following	the  heuristics  described  in
-       4mSOURCE24m  4mPRIORITY24m.  If	a  gem	is found in more than one global source,
+       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 1m:source0m
-       option or a 1msource 22mblock.
+       non-standard repository, suppressing this warning, by using the :source
+       option or a source block.
 
-   1mCREDENTIALS0m
+   CREDENTIALS
        Some gem sources require a username and password. Use bundle  config(1)
-       4mbundle-config.1.html24m  to  set  the username and password for any of the
+       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.
@@ -62,17 +62,18 @@ GEMFILE(5)							    GEMFILE(5)
 
 
        Credentials in the source URL will take precedence over credentials set
-       using 1mconfig22m.
+       using config.
 
-1mRUBY0m
+RUBY
        If your application requires a specific Ruby version or engine, specify
-       your  requirements using the 1mruby 22mmethod, with the following arguments.
-       All parameters are 1mOPTIONAL 22munless otherwise specified.
+       your  requirements using the ruby method, with the following arguments.
+       All parameters are OPTIONAL unless otherwise specified.
 
-   1mVERSION (required)0m
+   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.
 
 
 
@@ -80,14 +81,32 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mENGINE0m
-       Each application 4mmay24m specify a Ruby engine. If an engine is  specified,
-       an engine version 4mmust24m also be specified.
+   ENGINE
+       Each  application may specify a Ruby engine. If an engine is specified,
+       an engine version must also be specified.
 
-   1mENGINE VERSION0m
-       Each  application  4mmay24m specify a Ruby engine version. If an engine ver-
-       sion is specified, an engine 4mmust24m also be specified. If the  engine  is
-       "ruby" the engine version specified 4mmust24m match the Ruby version.
+       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   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.
+
+
+
+   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.
 
 
 
@@ -95,8 +114,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mPATCHLEVEL0m
-       Each application 4mmay24m specify a Ruby patchlevel.
+   PATCHLEVEL
+       Each application may specify a Ruby patchlevel.
 
 
 
@@ -104,12 +123,12 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-1mGEMS0m
-       Specify gem requirements using the 1mgem 22mmethod, with the following argu-
-       ments. All parameters are 1mOPTIONAL 22munless otherwise specified.
+GEMS
+       Specify gem requirements using the gem method, with the following argu-
+       ments. All parameters are OPTIONAL unless otherwise specified.
 
-   1mNAME (required)0m
-       For each gem requirement, list a single 4mgem24m line.
+   NAME (required)
+       For each gem requirement, list a single gem line.
 
 
 
@@ -117,8 +136,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mVERSION0m
-       Each 4mgem24m 1mMAY 22mhave one or more version specifiers.
+   VERSION
+       Each gem MAY have one or more version specifiers.
 
 
 
@@ -127,10 +146,10 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mREQUIRE AS0m
-       Each 4mgem24m 1mMAY 22mspecify files that should be used when  autorequiring  via
-       1mBundler.require22m.  You  may pass an array with multiple files or 1mtrue 22mif
-       file you want 1mrequired 22mhas same name as 4mgem24m or  1mfalse  22mto  prevent  any
+   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 from being autorequired.
 
 
@@ -152,9 +171,9 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mGROUPS0m
-       Each 4mgem24m 1mMAY 22mspecify membership in one or more  groups.  Any  4mgem24m  that
-       does  not  specify  membership  in  any	group is placed in the 1mdefault0m
+   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
        group.
 
 
@@ -164,8 +183,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       The Bundler runtime allows its  two  main  methods,  1mBundler.setup  22mand
-       1mBundler.require22m, to limit their impact to particular groups.
+       The Bundler runtime allows its  two  main  methods,  Bundler.setup  and
+       Bundler.require, to limit their impact to particular groups.
 
 
 
@@ -184,8 +203,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       The  Bundler CLI allows you to specify a list of groups whose gems 1mbun-0m
-       1mdle install 22mshould not install with the 1m--without  22moption.  To  specify
+       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.
 
@@ -196,46 +215,49 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       After running 1mbundle install --without test22m, bundler will remember that
+       After running bundle install --without test, bundler will remember that
        you excluded the test group in the last installation. The next time you
-       run 1mbundle install22m, without any 1m--without option22m, bundler  will  recall
+       run bundle install, without any --without option, bundler  will	recall
        it.
 
-       Also,  calling  1mBundler.setup	22mwith  no  parameters, or calling 1mrequire0m
-       1m"bundler/setup" 22mwill setup all groups except for the ones you  excluded
-       via 1m--without 22m(since they are not available).
+       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 1mbundle install22m, bundler downloads and evaluates all gems,
+       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 4mhttp://bundler.io/rationale.html24m.
+       Understanding Bundler http://bundler.io/rationale.html.
 
-   1mPLATFORMS0m
+   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 1m--without 22minstall-time
+       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 1mGemfile 22mplatforms:
+       There are a number of Gemfile platforms:
 
-       1mruby	22mC Ruby (MRI) or Rubinius, but 1mNOT 22mWindows
+       ruby   C Ruby (MRI), Rubinius or TruffleRuby, but NOT Windows
 
-       1mmri	22mSame as 4mruby24m, but not Rubinius
+       mri    Same as ruby, but only C Ruby (MRI)
 
-       1mmingw	22mWindows 32 bit 'mingw32' platform (aka RubyInstaller)
+       mingw  Windows 32 bit 'mingw32' platform (aka RubyInstaller)
 
-       1mx64_mingw0m
+       x64_mingw
 	      Windows 64 bit 'mingw32' platform (aka RubyInstaller x64)
 
-       1mrbx	22mSame as 4mruby24m, but only Rubinius (not MRI)
+       rbx    Rubinius
+
+       jruby  JRuby
 
-       1mjruby	22mJRuby
+       truffleruby
+	      TruffleRuby
 
-       1mmswin	22mWindows
+       mswin  Windows
 
        You can restrict further by platform  and  version  for	all  platforms
-       4mexcept24m for 1mrbx22m, 1mjruby22m, and 1mmswin22m.
+       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
@@ -249,13 +271,13 @@ GEMFILE(5)							    GEMFILE(5)
 
        The full list of platforms and supported versions includes:
 
-       1mruby	22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+       ruby   1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
 
-       1mmri	22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+       mri    1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
 
-       1mmingw	22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+       mingw  1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
 
-       1mx64_mingw0m
+       x64_mingw
 	      2.0, 2.1, 2.2, 2.3, 2.4, 2.5
 
        As with groups, you can specify one or more platforms:
@@ -268,11 +290,11 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       All   operations   involving  groups  (1mbundle	install22m,  1mBundler.setup22m,
-       1mBundler.require22m) behave exactly the same as if any groups not  matching
-       the current platform were explicitly excluded.
+       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.
 
-   1mSOURCE0m
+   SOURCE
        You  can  select  an  alternate Rubygems repository for a gem using the
        ':source' option.
 
@@ -289,47 +311,53 @@ GEMFILE(5)							    GEMFILE(5)
        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
-       4mSOURCE24m 4mPRIORITY24m.
+       SOURCE PRIORITY.
 
        Selecting  a  specific  source  repository this way also suppresses the
-       ambiguous gem warning described above in 4mGLOBAL24m 4mSOURCES24m 4m(#source)24m.
+       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.
 
-   1mGIT0m
+   GIT
        If necessary, you can specify that a gem is located at a particular git
-       repository using the 1m:git 22mparameter. The repository can be accessed via
+       repository using the :git parameter. The repository can be accessed via
        several protocols:
 
-       1mHTTP(S)0m
+       HTTP(S)
 	      gem "rails", :git => "https://github.com/rails/rails.git"
 
-       1mSSH	22mgem "rails", :git => "git@github.com:rails/rails.git"
+       SSH    gem "rails", :git => "git@github.com:rails/rails.git"
 
-       1mgit	22mgem "rails", :git => "git://github.com/rails/rails.git"
+       git    gem "rails", :git => "git://github.com/rails/rails.git"
 
-       If using SSH, the user that you use to run 1mbundle install MUST 22mhave the
-       appropriate keys available in their 1m$HOME/.ssh22m.
+       If using SSH, the user that you use to run bundle install MUST have the
+       appropriate keys available in their $HOME/.ssh.
 
-       1mNOTE22m:  1mhttp://  22mand  1mgit://	22mURLs 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 1mgroup22m, 1mplatforms22m, and 1mrequire  22moptions  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  1mSHOULD  22mhave  at least one file, at the root of the
-       directory containing the gem, with the extension  1m.gemspec22m.  This  file
-       1mMUST  22mcontain  a  valid gem specification, as expected by the 1mgem build0m
+       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 1m.gemspec22m, 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-
        erly integrate into your application.
 
-       If  a  git  repository does have a 1m.gemspec 22mfor the gem you attached it
+       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  1m.gemspec 22mspecifies a version matching the version
+       only  valid  if	the  .gemspec specifies a version matching the version
        specifier. If not, bundler will print a warning.
 
 
@@ -340,23 +368,35 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       If a git repository does 1mnot 22mhave a 1m.gemspec 22mfor the gem  you	attached
-       it to, a version specifier 1mMUST 22mbe provided. Bundler will use this ver-
-       sion in the simple 1m.gemspec 22mit creates.
+       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.
 
-       1mbranch22m, 1mtag22m, and 1mref0m
-	      You 1mMUST 22monly specify at most one of these options. The  default
-	      is 1m:branch => "master"0m
+       branch, tag, and ref
+	      You MUST only specify at most one of these options. The  default
+	      is :branch => "master"
 
-       1msubmodules0m
-	      Specify  1m:submodules => true 22mto cause bundler to expand any sub-
-	      modules included in the git repository
+       For example:
 
-       If a git repository contains multiple 1m.gemspecs22m, each  1m.gemspec  22mrepre-
-       sents  a  gem located at the same place in the file system as the 1m.gem-0m
-       1mspec22m.
+	      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
+
+	      git "https://github.com/rails/rails.git", :ref => "4aded" do
+
+       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
+
+       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.
 
 
 
@@ -371,13 +411,13 @@ GEMFILE(5)							    GEMFILE(5)
 
 
        To install a gem located in a git repository, bundler  changes  to  the
-       directory  containing the gemspec, runs 1mgem build name.gemspec 22mand then
-       installs the resulting gem. The 1mgem build 22mcommand, which comes standard
-       with  Rubygems,	evaluates the 1m.gemspec 22min the context of the directory
+       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
        in which it is located.
 
-   1mGIT SOURCE0m
-       A custom git source can be defined via the 1mgit_source	22mmethod.  Provide
+   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
        address:
@@ -397,9 +437,9 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mGITHUB0m
-       1mNOTE22m: This shorthand should be avoided until Bundler 2.0, since it cur-
-       rently expands to an insecure 1mgit:// 22mURL. This allows a man-in-the-mid-
+   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.
 
        If  the	git repository you want to use is hosted on GitHub and is pub-
@@ -423,10 +463,10 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       Since the 1mgithub 22mmethod is a specialization of 1mgit_source22m, it accepts a
-       1m:branch 22mnamed argument.
+       Since the github method is a specialization of git_source, it accepts a
+       :branch named argument.
 
-   1mGIST0m
+   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
        (without the trailing ".git").
@@ -445,10 +485,10 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       Since the 1mgist 22mmethod is a specialization of 1mgit_source22m, it  accepts  a
-       1m:branch 22mnamed argument.
+       Since the gist method is a specialization of git_source, it  accepts  a
+       :branch named argument.
 
-   1mBITBUCKET0m
+   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
@@ -470,19 +510,19 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       Since  the  1mbitbucket	22mmethod  is  a  specialization  of 1mgit_source22m, it
-       accepts a 1m:branch 22mnamed argument.
+       Since  the  bitbucket  method  is  a  specialization  of git_source, it
+       accepts a :branch named argument.
 
-   1mPATH0m
+   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 1mGemfile22m.
+       taining the Gemfile.
 
-       Similar to the semantics of the 1m:git 22moption, the 1m:path 22moption	requires
-       that  the directory in question either contains a 1m.gemspec 22mfor 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 1m:git22m, bundler does not compile C extensions for  gems  specified
+       Unlike :git, bundler does not compile C extensions for  gems  specified
        as paths.
 
 
@@ -492,8 +532,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
        If you would like to use multiple local gems directly from the filesys-
-       tem, you can set a global 1mpath 22moption 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.
 
 
 
@@ -504,8 +544,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-1mBLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS0m
-       The 1m:source22m, 1m:git22m, 1m:path22m, 1m:group22m, and 1m:platforms 22moptions may be applied
+BLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS
+       The :source, :git, :path, :group, and :platforms options may be applied
        to a group of gems by using block form.
 
 
@@ -532,16 +572,23 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       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 1m--with0m
-       option given to the 1mbundle install 22mcommand.
+       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 1mgit 22mblock form, the 1m:ref22m, 1m:branch22m, 1m:tag22m,	and  1m:sub-0m
-       1mmodules  22moptions  may  be passed to the 1mgit 22mmethod, 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.
 
-1mINSTALL_IF0m
-       The 1minstall_if 22mmethod allows gems to be installed based on	a  proc  or
+       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
        used if certain software is installed or some other conditions are met.
 
@@ -553,48 +600,54 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-1mGEMSPEC0m
+GEMSPEC
+       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
+       run.
+
        If you wish to use Bundler to help install dependencies for a gem while
-       it  is being developed, use the 1mgemspec 22mmethod to pull in the dependen-
-       cies listed in the 1m.gemspec 22mfile.
+       it is being developed, use the gemspec method to pull in the  dependen-
+       cies listed in the .gemspec file.
 
-       The 1mgemspec 22mmethod adds any runtime dependencies as gem requirements in
-       the  default  group.  It  also  adds  development  dependencies	as gem
-       requirements in the 1mdevelopment 22mgroup. Finally, it adds a gem  require-
-       ment on your project (1m:path => '.'22m). In conjunction with 1mBundler.setup22m,
+       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
+       if the project were installed as a gem; you  need  not  manipulate  the
        load path manually or require project files via relative paths.
 
-       The 1mgemspec 22mmethod supports optional 1m:path22m, 1m:glob22m, 1m:name22m, and 1m:develop-0m
-       1mment_group 22moptions, which control where bundler looks for the 1m.gemspec22m,
-       the glob it uses to look for the  gemspec  (defaults  to:  "{,4m,24m/*}.gem-
-       spec"),	what named 1m.gemspec 22mit uses (if more than one is present), and
+       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 1mgemspec 22mdependency 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 1mgemspec 22mgem.
+       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.
 
-1mSOURCE PRIORITY0m
-       When  attempting  to locate a gem to satisfy a gem requirement, bundler
+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 1m:source22m, 1m:path22m, or
-	   1m:git22m)
+       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
-	   over ones from 1mrubygems.org0m
+	   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  1msource  22mlines,  searching  each
-	   source in your 1mGemfile 22mfrom last added to first added.
+       3.  The	sources  specified  via  global  source  lines, searching each
+	   source in your Gemfile from last added to first added.
 
 
 
 
 
 
-				   May 2017			    GEMFILE(5)
+				 November 2018			    GEMFILE(5)