bundler 1.13.6 → 1.17.3

data/bin/rspec

@@ -1,15 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-load File.expand_path("../with_rubygems", __FILE__) if ENV["RGV"]
-
-require "rubygems"
-
-bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__))
-bundler_spec.dependencies.each do |dep|
-  gem dep.name, dep.requirement
-end
-
-Gem.finish_resolve if Gem.respond_to?(:finish_resolve)
-
-load Gem.bin_path("rspec-core", "rspec")

data/bin/rubocop

@@ -1,17 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-load File.expand_path("../with_rubygems", __FILE__) if ENV["RGV"]
-
-require "rubygems"
-
-bundler_spec = Gem::Specification.load(File.expand_path("../../bundler.gemspec", __FILE__))
-bundler_spec.dependencies.each do |dep|
-  gem dep.name, dep.requirement
-end
-
-gem "rubocop", "= 0.41.2"
-
-Gem.finish_resolve if Gem.respond_to?(:finish_resolve)
-
-load Gem.bin_path("rubocop", "rubocop")

data/bin/with_rubygems

@@ -1,39 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require "pathname"
-
-def run(*cmd)
-  return if system(*cmd)
-  raise "Running `#{cmd.join(" ")}` failed"
-end
-
-version = ENV.delete("RGV")
-rubygems_path = Pathname.new(__FILE__).join("../../tmp/rubygems").expand_path
-unless rubygems_path.directory?
-  rubygems_path.parent.mkpath unless rubygems_path.directory?
-  run("git", "clone", "https://github.com/rubygems/rubygems.git", rubygems_path.to_s)
-end
-Dir.chdir(rubygems_path) do
-  version = "v#{version}" if version =~ /\A\d/
-  run("git", "checkout", version, "--quiet")
-end if version
-
-rubygems_lib = rubygems_path + "lib"
-ENV["RUBYOPT"] = %(-I#{rubygems_lib} #{ENV["RUBYOPT"]})
-
-if $0 != __FILE__
-  ARGV.unshift($0)
-elsif cmd = ARGV.first
-  possible_dirs = [
-    Pathname.new(__FILE__) + "..",
-    Pathname.new(__FILE__) + "../../exe",
-    rubygems_path + "bin",
-  ]
-  cmd = possible_dirs.map do |dir|
-    dir.join(cmd).expand_path
-  end.find(&:file?)
-  ARGV[0] = cmd.to_s if cmd
-end
-
-exec(*ARGV)

data/lib/bundler/man/bundle-binstubs.txt

@@ -1,33 +0,0 @@
-BUNDLE-BINSTUBS(1)					    BUNDLE-BINSTUBS(1)
-
-
-
-1mNAME0m
-       1mbundle-binstubs 22m- Install the binstubs of the listed gems
-
-1mSYNOPSIS0m
-       1mbundle binstubs 4m22mGEM_NAME24m [--force] [--path PATH] [--standalone]
-
-1mDESCRIPTION0m
-       This  command  generates binstubs for executables in 1mGEM_NAME22m. Binstubs
-       are put into 1mbin22m, or the 1m--path 22mdirectory if one has been set.  Calling
-       binstubs with [GEM [GEM]] will create binstubs for all given gems.
-
-1mOPTIONS0m
-       1m--force0m
-	      Overwrite existing binstubs if they exist.
-
-       1m--path 22mThe location to install the specified binstubs to. This defaults
-	      to 1mbin22m.
-
-       1m--standalone0m
-	      Makes binstubs that can work without depending  on  Rubygems  or
-	      Bundler at runtime.
-
-1mBUNDLE INSTALL --BINSTUBS0m
-       To  create  binstubs  for  all  the  gems in the bundle you can use the
-       1m--binstubs 22mflag in bundle install(1) 4mbundle-install.1.html24m.
-
-
-
-				 October 2016		    BUNDLE-BINSTUBS(1)

data/lib/bundler/man/bundle-config

@@ -1,254 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "BUNDLE\-CONFIG" "1" "October 2016" "" ""
-.
-.SH "NAME"
-\fBbundle\-config\fR \- Set bundler configuration options
-.
-.SH "SYNOPSIS"
-\fBbundle config\fR [\fIname\fR [\fIvalue\fR]]
-.
-.SH "DESCRIPTION"
-This command allows you to interact with bundler\'s configuration system\. Bundler retrieves its configuration from the local application (\fBapp/\.bundle/config\fR), environment variables, and the user\'s home directory (\fB~/\.bundle/config\fR), in that order of priority\.
-.
-.P
-Executing \fBbundle config\fR with no parameters will print a list of all bundler configuration for the current bundle, and where that configuration was set\.
-.
-.P
-Executing \fBbundle config <name>\fR will print the value of that configuration setting, and where it was set\.
-.
-.P
-Executing \fBbundle config <name> <value>\fR will set that configuration to the value specified for all bundles executed as the current user\. The configuration will be stored in \fB~/\.bundle/config\fR\. If \fIname\fR already is set, \fIname\fR will be overridden and user will be warned\.
-.
-.P
-Executing \fBbundle config \-\-global <name> <value>\fR works the same as above\.
-.
-.P
-Executing \fBbundle config \-\-local <name> <value>\fR will set that configuration to the local application\. The configuration will be stored in \fBapp/\.bundle/config\fR\.
-.
-.P
-Executing \fBbundle config \-\-delete <name>\fR will delete the configuration in both local and global sources\. Not compatible with \-\-global or \-\-local flag\.
-.
-.P
-Executing bundle with the \fBBUNDLE_IGNORE_CONFIG\fR environment variable set will cause it to ignore all configuration\.
-.
-.P
-Executing \fBbundle config disable_multisource true\fR upgrades the warning about the Gemfile containing multiple primary sources to an error\. Executing \fBbundle config \-\-delete disable_multisource\fR downgrades this error to a warning\.
-.
-.SH "REMEMBERING OPTIONS"
-Flags passed to \fBbundle install\fR or the Bundler runtime, such as \fB\-\-path foo\fR or \fB\-\-without production\fR, are not remembered between commands\. If these options must be remembered,they must be set using \fBbundle config\fR (e\.g\., \fBbundle config path foo\fR)\.
-.
-.P
-The options that can be configured are:
-.
-.TP
-\fBbinstubs\fR
-Creates a directory (defaults to \fB~/bin\fR) and place any executables from the gem there\. These executables run in Bundler\'s context\. If used, you might add this directory to your environment\'s \fBPATH\fR variable\. For instance, if the \fBrails\fR gem comes with a \fBrails\fR executable, this flag will create a \fBbin/rails\fR executable that ensures that all referred dependencies will be resolved using the bundled gems\.
-.
-.TP
-\fBdeployment\fR
-In deployment mode, Bundler will \'roll\-out\' the bundle for \fBproduction\fR use\. Please check carefully if you want to have this option enabled in \fBdevelopment\fR or \fBtest\fR environments\.
-.
-.TP
-\fBpath\fR
-The location to install the specified gems to\. This defaults to Rubygems\' setting\. Bundler shares this location with Rubygems, \fBgem install \.\.\.\fR will have gem installed there, too\. Therefore, gems installed without a \fB\-\-path \.\.\.\fR setting will show up by calling \fBgem list\fR\. Accodingly, gems installed to other locations will not get listed\.
-.
-.TP
-\fBwithout\fR
-A space\-separated list of groups referencing gems to skip during installation\.
-.
-.SH "BUILD OPTIONS"
-You can use \fBbundle config\fR to give bundler the flags to pass to the gem installer every time bundler tries to install a particular gem\.
-.
-.P
-A very common example, the \fBmysql\fR gem, requires Snow Leopard users to pass configuration flags to \fBgem install\fR to specify where to find the \fBmysql_config\fR executable\.
-.
-.IP "" 4
-.
-.nf
-
-gem install mysql \-\- \-\-with\-mysql\-config=/usr/local/mysql/bin/mysql_config
-.
-.fi
-.
-.IP "" 0
-.
-.P
-Since the specific location of that executable can change from machine to machine, you can specify these flags on a per\-machine basis\.
-.
-.IP "" 4
-.
-.nf
-
-bundle config build\.mysql \-\-with\-mysql\-config=/usr/local/mysql/bin/mysql_config
-.
-.fi
-.
-.IP "" 0
-.
-.P
-After running this command, every time bundler needs to install the \fBmysql\fR gem, it will pass along the flags you specified\.
-.
-.SH "CONFIGURATION KEYS"
-Configuration keys in bundler have two forms: the canonical form and the environment variable form\.
-.
-.P
-For instance, passing the \fB\-\-without\fR flag to bundle install(1) \fIbundle\-install\.1\.html\fR prevents Bundler from installing certain groups specified in the Gemfile(5)\. Bundler persists this value in \fBapp/\.bundle/config\fR so that calls to \fBBundler\.setup\fR do not try to find gems from the \fBGemfile\fR that you didn\'t install\. Additionally, subsequent calls to bundle install(1) \fIbundle\-install\.1\.html\fR remember this setting and skip those groups\.
-.
-.P
-The canonical form of this configuration is \fB"without"\fR\. To convert the canonical form to the environment variable form, capitalize it, and prepend \fBBUNDLE_\fR\. The environment variable form of \fB"without"\fR is \fBBUNDLE_WITHOUT\fR\.
-.
-.P
-Any periods in the configuration keys must be replaced with two underscores when setting it via environment variables\. The configuration key \fBlocal\.rack\fR becomes the environment variable \fBBUNDLE_LOCAL__RACK\fR\.
-.
-.SH "LIST OF AVAILABLE KEYS"
-The following is a list of all configuration keys and their purpose\. You can learn more about their operation in bundle install(1) \fIbundle\-install\.1\.html\fR\.
-.
-.IP "\(bu" 4
-\fBpath\fR (\fBBUNDLE_PATH\fR): The location on disk where all gems in your bundle will be located regardless of \fB$GEM_HOME\fR or \fB$GEM_PATH\fR values\. Bundle gems not found in this location will be installed by \fBbundle install\fR\. Defaults to \fBGem\.dir\fR\. When \-\-deployment is used, defaults to vendor/bundle\.
-.
-.IP "\(bu" 4
-\fBfrozen\fR (\fBBUNDLE_FROZEN\fR): Disallow changes to the \fBGemfile\fR\. Defaults to \fBtrue\fR when \fB\-\-deployment\fR is used\.
-.
-.IP "\(bu" 4
-\fBwithout\fR (\fBBUNDLE_WITHOUT\fR): A \fB:\fR\-separated list of groups whose gems bundler should not install
-.
-.IP "\(bu" 4
-\fBbin\fR (\fBBUNDLE_BIN\fR): Install executables from gems in the bundle to the specified directory\. Defaults to \fBfalse\fR\.
-.
-.IP "\(bu" 4
-\fBgemfile\fR (\fBBUNDLE_GEMFILE\fR): The name of the file that bundler should use as the \fBGemfile\fR\. This location of this file also sets the root of the project, which is used to resolve relative paths in the \fBGemfile\fR, among other things\. By default, bundler will search up from the current working directory until it finds a \fBGemfile\fR\.
-.
-.IP "\(bu" 4
-\fBssl_ca_cert\fR (\fBBUNDLE_SSL_CA_CERT\fR): Path to a designated CA certificate file or folder containing multiple certificates for trusted CAs in PEM format\.
-.
-.IP "\(bu" 4
-\fBssl_client_cert\fR (\fBBUNDLE_SSL_CLIENT_CERT\fR): Path to a designated file containing a X\.509 client certificate and key in PEM format\.
-.
-.IP "\(bu" 4
-\fBcache_path\fR (\fBBUNDLE_CACHE_PATH\fR): The directory that bundler will place cached gems in when running \fBbundle package\fR, and that bundler will look in when installing gems\.
-.
-.IP "\(bu" 4
-\fBdisable_multisource\fR (\fBBUNDLE_DISABLE_MULTISOURCE\fR): When set, Gemfiles containing multiple sources will produce errors instead of warnings\. Use \fBbundle config \-\-delete disable_multisource\fR to unset\.
-.
-.IP "\(bu" 4
-\fBignore_messages\fR (\fBBUNDLE_IGNORE_MESSAGES\fR): When set, no post install messages will be printed\. To silence a single gem, use dot notation like \fBignore_messages\.httparty true\fR\.
-.
-.IP "\(bu" 4
-\fBretry\fR (\fBBUNDLE_RETRY\fR): The number of times to retry failed network requests\. Defaults to \fB3\fR\.
-.
-.IP "\(bu" 4
-\fBredirect\fR (\fBBUNDLE_REDIRECT\fR): The number of redirects allowed for network requests\. Defaults to \fB5\fR\.
-.
-.IP "\(bu" 4
-\fBtimeout\fR (\fBBUNDLE_TIMEOUT\fR): The seconds allowed before timing out for network requests\. Defaults to \fB10\fR\.
-.
-.IP "" 0
-.
-.P
-In general, you should set these settings per\-application by using the applicable flag to the bundle install(1) \fIbundle\-install\.1\.html\fR or bundle package(1) \fIbundle\-package\.1\.html\fR command\.
-.
-.P
-You can set them globally either via environment variables or \fBbundle config\fR, whichever is preferable for your setup\. If you use both, environment variables will take preference over global settings\.
-.
-.SH "LOCAL GIT REPOS"
-Bundler also allows you to work against a git repository locally instead of using the remote version\. This can be achieved by setting up a local override:
-.
-.IP "" 4
-.
-.nf
-
-bundle config local\.GEM_NAME /path/to/local/git/repository
-.
-.fi
-.
-.IP "" 0
-.
-.P
-For example, in order to use a local Rack repository, a developer could call:
-.
-.IP "" 4
-.
-.nf
-
-bundle config local\.rack ~/Work/git/rack
-.
-.fi
-.
-.IP "" 0
-.
-.P
-Now instead of checking out the remote git repository, the local override will be used\. Similar to a path source, every time the local git repository change, changes will be automatically picked up by Bundler\. This means a commit in the local git repo will update the revision in the \fBGemfile\.lock\fR to the local git repo revision\. This requires the same attention as git submodules\. Before pushing to the remote, you need to ensure the local override was pushed, otherwise you may point to a commit that only exists in your local machine\.
-.
-.P
-Bundler does many checks to ensure a developer won\'t work with invalid references\. Particularly, we force a developer to specify a branch in the \fBGemfile\fR in order to use this feature\. If the branch specified in the \fBGemfile\fR and the current branch in the local git repository do not match, Bundler will abort\. This ensures that a developer is always working against the correct branches, and prevents accidental locking to a different branch\.
-.
-.P
-Finally, Bundler also ensures that the current revision in the \fBGemfile\.lock\fR exists in the local git repository\. By doing this, Bundler forces you to fetch the latest changes in the remotes\.
-.
-.SH "MIRRORS OF GEM SOURCES"
-Bundler supports overriding gem sources with mirrors\. This allows you to configure rubygems\.org as the gem source in your Gemfile while still using your mirror to fetch gems\.
-.
-.IP "" 4
-.
-.nf
-
-bundle config mirror\.SOURCE_URL MIRROR_URL
-.
-.fi
-.
-.IP "" 0
-.
-.P
-For example, to use a mirror of rubygems\.org hosted at
-.
-.IP "" 4
-.
-.nf
-
-bundle config mirror\.http://rubygems\.org http://rubygems\-mirror\.org
-.
-.fi
-.
-.IP "" 0
-.
-.SH "CREDENTIALS FOR GEM SOURCES"
-Bundler allows you to configure credentials for any gem source, which allows you to avoid putting secrets into your Gemfile\.
-.
-.IP "" 4
-.
-.nf
-
-bundle config SOURCE_HOSTNAME USERNAME:PASSWORD
-.
-.fi
-.
-.IP "" 0
-.
-.P
-For example, to save the credentials of user \fBclaudette\fR for the gem source at \fBgems\.longerous\.com\fR, you would run:
-.
-.IP "" 4
-.
-.nf
-
-bundle config gems\.longerous\.com claudette:s00pers3krit
-.
-.fi
-.
-.IP "" 0
-.
-.P
-Or you can set the credentials as an environment variable like this:
-.
-.IP "" 4
-.
-.nf
-
-export BUNDLE_GEMS__LONGEROUS__COM="claudette:s00pers3krit"
-.
-.fi
-.
-.IP "" 0
-

data/lib/bundler/man/bundle-config.txt

@@ -1,282 +0,0 @@
-BUNDLE-CONFIG(1)					      BUNDLE-CONFIG(1)
-
-
-
-1mNAME0m
-       1mbundle-config 22m- Set bundler configuration options
-
-1mSYNOPSIS0m
-       1mbundle config 22m[4mname24m [4mvalue24m]]
-
-1mDESCRIPTION0m
-       This  command  allows you to interact with bundler's configuration sys-
-       tem. Bundler retrieves its configuration  from  the  local  application
-       (1mapp/.bundle/config22m), environment variables, and the user's home direc-
-       tory (1m~/.bundle/config22m), in that order of priority.
-
-       Executing 1mbundle config 22mwith no parameters will print  a  list  of	all
-       bundler configuration for the current bundle, and where that configura-
-       tion was set.
-
-       Executing 1mbundle config <name> 22mwill print the value of that  configura-
-       tion setting, and where it was set.
-
-       Executing  1mbundle  config <name> <value> 22mwill set that configuration to
-       the value specified for all bundles executed as the current  user.  The
-       configuration  will  be	stored in 1m~/.bundle/config22m. If 4mname24m already is
-       set, 4mname24m will be overridden and user will be warned.
-
-       Executing 1mbundle config --global  <name>  <value>  22mworks  the  same  as
-       above.
-
-       Executing 1mbundle config --local <name> <value> 22mwill set that configura-
-       tion to the local application. The  configuration  will	be  stored  in
-       1mapp/.bundle/config22m.
-
-       Executing  1mbundle  config --delete <name> 22mwill delete the configuration
-       in both local and global  sources.  Not	compatible  with  --global  or
-       --local flag.
-
-       Executing bundle with the 1mBUNDLE_IGNORE_CONFIG 22menvironment variable set
-       will cause it to ignore all configuration.
-
-       Executing 1mbundle config disable_multisource true 22mupgrades  the  warning
-       about the Gemfile containing multiple primary sources to an error. Exe-
-       cuting 1mbundle config --delete disable_multisource 22mdowngrades this error
-       to a warning.
-
-1mREMEMBERING OPTIONS0m
-       Flags  passed  to 1mbundle install 22mor the Bundler runtime, such as 1m--path0m
-       1mfoo 22mor 1m--without production22m, are not remembered  between  commands.  If
-       these  options  must be remembered,they must be set using 1mbundle config0m
-       (e.g., 1mbundle config path foo22m).
-
-       The options that can be configured are:
-
-       1mbinstubs0m
-	      Creates a directory (defaults to 1m~/bin22m) and place  any  executa-
-	      bles from the gem there. These executables run in Bundler's con-
-	      text. If used, you might add this  directory  to	your  environ-
-	      ment's  1mPATH 22mvariable. For instance, if the 1mrails 22mgem comes with
-	      a 1mrails 22mexecutable, this flag will create a 1mbin/rails 22mexecutable
-	      that  ensures  that  all	referred dependencies will be resolved
-	      using the bundled gems.
-
-       1mdeployment0m
-	      In deployment mode, Bundler will 'roll-out' the bundle for  1mpro-0m
-	      1mduction  22muse.  Please  check  carefully if you want to have this
-	      option enabled in 1mdevelopment 22mor 1mtest 22menvironments.
-
-       1mpath	22mThe location to install the specified gems to. This defaults  to
-	      Rubygems'  setting.  Bundler shares this location with Rubygems,
-	      1mgem install ... 22mwill have gem installed there,  too.  Therefore,
-	      gems  installed  without	a  1m--path  ... 22msetting will show up by
-	      calling 1mgem list22m. Accodingly, gems installed to other  locations
-	      will not get listed.
-
-       1mwithout0m
-	      A space-separated list of groups referencing gems to skip during
-	      installation.
-
-1mBUILD OPTIONS0m
-       You can use 1mbundle config 22mto give bundler the flags to pass to the	gem
-       installer every time bundler tries to install a particular gem.
-
-       A  very	common	example, the 1mmysql 22mgem, requires Snow Leopard users to
-       pass configuration flags to 1mgem install 22mto specify where  to  find	the
-       1mmysql_config 22mexecutable.
-
-
-
-	   gem install mysql -- --with-mysql-config=/usr/local/mysql/bin/mysql_config
-
-
-
-       Since  the specific location of that executable can change from machine
-       to machine, you can specify these flags on a per-machine basis.
-
-
-
-	   bundle config build.mysql --with-mysql-config=/usr/local/mysql/bin/mysql_config
-
-
-
-       After running this command, every time bundler  needs  to  install  the
-       1mmysql 22mgem, it will pass along the flags you specified.
-
-1mCONFIGURATION KEYS0m
-       Configuration  keys  in	bundler have two forms: the canonical form and
-       the environment variable form.
-
-       For instance, passing the 1m--without  22mflag  to  bundle  install(1)  4mbun-0m
-       4mdle-install.1.html24m	prevents  Bundler  from  installing  certain groups
-       specified in the Gemfile(5). Bundler persists this value  in  1mapp/.bun-0m
-       1mdle/config  22mso that calls to 1mBundler.setup 22mdo not try to find gems from
-       the 1mGemfile 22mthat you didn't install. Additionally, subsequent calls  to
-       bundle  install(1) 4mbundle-install.1.html24m remember this setting and skip
-       those groups.
-
-       The canonical form of this configuration is 1m"without"22m. To  convert	the
-       canonical  form	to  the  environment variable form, capitalize it, and
-       prepend 1mBUNDLE_22m. The environment variable form  of	1m"without"  22mis  1mBUN-0m
-       1mDLE_WITHOUT22m.
-
-       Any  periods in the configuration keys must be replaced with two under-
-       scores when setting it via environment variables. The configuration key
-       1mlocal.rack 22mbecomes the environment variable 1mBUNDLE_LOCAL__RACK22m.
-
-1mLIST OF AVAILABLE KEYS0m
-       The  following  is  a list of all configuration keys and their purpose.
-       You can learn more about their  operation  in  bundle  install(1)  4mbun-0m
-       4mdle-install.1.html24m.
-
-       o   1mpath  22m(1mBUNDLE_PATH22m):  The	location  on disk where all gems in your
-	   bundle will be located regardless of 1m$GEM_HOME 22mor 1m$GEM_PATH 22mvalues.
-	   Bundle  gems not found in this location will be installed by 1mbundle0m
-	   1minstall22m. Defaults to 1mGem.dir22m. When --deployment is  used,	defaults
-	   to vendor/bundle.
-
-       o   1mfrozen  22m(1mBUNDLE_FROZEN22m):  Disallow changes to the 1mGemfile22m. Defaults
-	   to 1mtrue 22mwhen 1m--deployment 22mis used.
-
-       o   1mwithout 22m(1mBUNDLE_WITHOUT22m): A 1m:22m-separated list of groups  whose  gems
-	   bundler should not install
-
-       o   1mbin  22m(1mBUNDLE_BIN22m):  Install  executables from gems in the bundle to
-	   the specified directory. Defaults to 1mfalse22m.
-
-       o   1mgemfile 22m(1mBUNDLE_GEMFILE22m): The name of the file that bundler  should
-	   use	as  the 1mGemfile22m. This location of this file also sets the root
-	   of the project, which is used to resolve relative paths in the 1mGem-0m
-	   1mfile22m,  among  other things. By default, bundler will search up from
-	   the current working directory until it finds a 1mGemfile22m.
-
-       o   1mssl_ca_cert 22m(1mBUNDLE_SSL_CA_CERT22m): Path to a designated CA	certifi-
-	   cate  file  or  folder containing multiple certificates for trusted
-	   CAs in PEM format.
-
-       o   1mssl_client_cert 22m(1mBUNDLE_SSL_CLIENT_CERT22m): Path to a designated file
-	   containing a X.509 client certificate and key in PEM format.
-
-       o   1mcache_path  22m(1mBUNDLE_CACHE_PATH22m):  The  directory  that bundler will
-	   place cached gems in when running 1mbundle package22m, and that  bundler
-	   will look in when installing gems.
-
-       o   1mdisable_multisource  22m(1mBUNDLE_DISABLE_MULTISOURCE22m):  When  set, Gem-
-	   files containing multiple sources will produce  errors  instead  of
-	   warnings. Use 1mbundle config --delete disable_multisource 22mto unset.
-
-       o   1mignore_messages 22m(1mBUNDLE_IGNORE_MESSAGES22m): When set, no post install
-	   messages will be printed. To silence a single gem, use dot notation
-	   like 1mignore_messages.httparty true22m.
-
-       o   1mretry  22m(1mBUNDLE_RETRY22m):  The number of times to retry failed network
-	   requests. Defaults to 1m322m.
-
-       o   1mredirect 22m(1mBUNDLE_REDIRECT22m): The number  of  redirects  allowed  for
-	   network requests. Defaults to 1m522m.
-
-       o   1mtimeout 22m(1mBUNDLE_TIMEOUT22m): The seconds allowed before timing out for
-	   network requests. Defaults to 1m1022m.
-
-
-
-       In general, you should set these settings per-application by using  the
-       applicable  flag to the bundle install(1) 4mbundle-install.1.html24m or bun-
-       dle package(1) 4mbundle-package.1.html24m command.
-
-       You can set them globally either via environment  variables  or	1mbundle0m
-       1mconfig22m,  whichever is preferable for your setup. If you use both, envi-
-       ronment variables will take preference over global settings.
-
-1mLOCAL GIT REPOS0m
-       Bundler also allows you	to  work  against  a  git  repository  locally
-       instead of using the remote version. This can be achieved by setting up
-       a local override:
-
-
-
-	   bundle config local.GEM_NAME /path/to/local/git/repository
-
-
-
-       For example, in order to use a local Rack repository, a developer could
-       call:
-
-
-
-	   bundle config local.rack ~/Work/git/rack
-
-
-
-       Now  instead of checking out the remote git repository, the local over-
-       ride will be used. Similar to a path source, every time the  local  git
-       repository  change, changes will be automatically picked up by Bundler.
-       This means a commit in the local git repo will update the  revision  in
-       the 1mGemfile.lock 22mto the local git repo revision. This requires the same
-       attention as git submodules. Before pushing to the remote, you need  to
-       ensure the local override was pushed, otherwise you may point to a com-
-       mit that only exists in your local machine.
-
-       Bundler does many checks to ensure a developer won't work with  invalid
-       references.  Particularly,  we force a developer to specify a branch in
-       the 1mGemfile 22min order to use this feature. If the  branch  specified  in
-       the  1mGemfile  22mand the current branch in the local git repository do not
-       match, Bundler will abort. This ensures	that  a  developer  is	always
-       working	against  the correct branches, and prevents accidental locking
-       to a different branch.
-
-       Finally, Bundler also ensures that the current  revision  in  the  1mGem-0m
-       1mfile.lock  22mexists  in  the local git repository. By doing this, Bundler
-       forces you to fetch the latest changes in the remotes.
-
-1mMIRRORS OF GEM SOURCES0m
-       Bundler supports overriding gem sources with mirrors. This  allows  you
-       to configure rubygems.org as the gem source in your Gemfile while still
-       using your mirror to fetch gems.
-
-
-
-	   bundle config mirror.SOURCE_URL MIRROR_URL
-
-
-
-       For example, to use a mirror of rubygems.org hosted at
-
-
-
-	   bundle config mirror.http://rubygems.org http://rubygems-mirror.org
-
-
-
-1mCREDENTIALS FOR GEM SOURCES0m
-       Bundler allows you to configure credentials for any gem	source,  which
-       allows you to avoid putting secrets into your Gemfile.
-
-
-
-	   bundle config SOURCE_HOSTNAME USERNAME:PASSWORD
-
-
-
-       For  example,  to  save	the  credentials of user 1mclaudette 22mfor the gem
-       source at 1mgems.longerous.com22m, you would run:
-
-
-
-	   bundle config gems.longerous.com claudette:s00pers3krit
-
-
-
-       Or you can set the credentials as an environment variable like this:
-
-
-
-	   export BUNDLE_GEMS__LONGEROUS__COM="claudette:s00pers3krit"
-
-
-
-
-
-
-				 October 2016		      BUNDLE-CONFIG(1)