bundler 1.13.6 → 1.17.3

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

@@ -1,52 +0,0 @@
-BUNDLE-LOCK(1)							BUNDLE-LOCK(1)
-
-
-
-1mNAME0m
-       1mbundle-lock 22m- Creates / Updates a lockfile without installing
-
-1mSYNOPSIS0m
-       1mbundle lock 22m[--update] [--local] [--print] [--lockfile=PATH]
-
-1mDESCRIPTION0m
-       Lock the gems specified in Gemfile.
-
-1mOPTIONS0m
-       1m--update=<*gems>0m
-	      Ignores  the  existing  lockfile. Resolve then updates lockfile.
-	      Taking a list of gems or updating all gems if no list is given.
-
-       1m--local0m
-	      Do not attempt to connect to 1mrubygems.org22m. Instead, Bundler will
-	      use  the	gems  already  present	in  Rubygems' cache or in 1mven-0m
-	      1mdor/cache22m. Note that  if  a	appropriate  platform-specific	gem
-	      exists on 1mrubygems.org 22mit will not be found.
-
-       1m--print0m
-	      Prints  the  lockfile  to  STDOUT instead of writing to the file
-	      system.
-
-       1m--lockfile=<path>0m
-	      The path where the lockfile should be written to.
-
-1mUPDATING ALL GEMS0m
-       If you run 1mbundle lock 22mwith  1m--update  22moption	without  list  of  gems,
-       bundler	will  ignore  any  previously  installed  gems and resolve all
-       dependencies again based on the latest versions of all  gems  available
-       in the sources.
-
-1mUPDATING A LIST OF GEMS0m
-       Sometimes, you want to update a single gem in the Gemfile(5), and leave
-       the rest of the gems that you specified locked to the versions  in  the
-       1mGemfile.lock22m.
-
-       For  instance,  you  only  want	to  update  1mnokogiri22m,  run 1mbundle lock0m
-       1m--update nokogiri22m.
-
-       Bundler will update 1mnokogiri 22mand any of its dependencies, but leave the
-       rest  of the gems that you specified locked to the versions in the 1mGem-0m
-       1mfile.lock22m.
-
-
-
-				   June 2016			BUNDLE-LOCK(1)

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

@@ -1,74 +0,0 @@
-BUNDLE-PACKAGE(1)					     BUNDLE-PACKAGE(1)
-
-
-
-1mNAME0m
-       1mbundle-package 22m- Package your needed 1m.gem 22mfiles into your application
-
-1mSYNOPSIS0m
-       1mbundle package0m
-
-1mDESCRIPTION0m
-       Copy  all of the 1m.gem 22mfiles needed to run the application into the 1mven-0m
-       1mdor/cache 22mdirectory. In the future, when running bundle install(1) 4mbun-0m
-       4mdle-install.1.html24m, use the gems in the cache in preference to the ones
-       on 1mrubygems.org22m.
-
-1mGIT AND PATH GEMS0m
-       Since Bundler 1.2, the 1mbundle package 22mcommand can also package 1m:git 22mand
-       1m:path	22mdependencies  besides  .gem	files.	This needs to be explicitly
-       enabled via the 1m--all 22moption. Once	used,  the  1m--all  22moption	will  be
-       remembered.
-
-1mSUPPORT FOR MULTIPLE PLATFORMS0m
-       When  using  gems that have different packages for different platforms,
-       Bundler 1.8 and newer support caching of gems for other platforms where
-       the  Gemfile  has  been resolved (i.e. present in the lockfile) in 1mven-0m
-       1mdor/cache22m. This needs to be enabled  via  the  1m--all-platforms  22moption.
-       This setting will be remembered in your local bundler configuration.
-
-1mREMOTE FETCHING0m
-       By  default,  if  you run bundle install(1) 4mbundle-install.1.html24m after
-       running bundle package(1)  4mbundle-package.1.html24m,  bundler	will  still
-       connect to 1mrubygems.org 22mto check whether a platform-specific gem exists
-       for any of the gems in 1mvendor/cache22m.
-
-       For instance, consider this Gemfile(5):
-
-
-
-	   source "https://rubygems.org"
-
-	   gem "nokogiri"
-
-
-
-       If you run 1mbundle package 22munder C Ruby, bundler will retrieve the  ver-
-       sion  of  1mnokogiri  22mfor the 1m"ruby" 22mplatform. If you deploy to JRuby and
-       run 1mbundle install22m, bundler is forced to check to see whether a  1m"java"0m
-       platformed 1mnokogiri 22mexists.
-
-       Even  though  the  1mnokogiri  22mgem  for  the Ruby platform is 4mtechnically0m
-       acceptable on JRuby, it has a C extension that does not run  on	JRuby.
-       As a result, bundler will, by default, still connect to 1mrubygems.org 22mto
-       check whether it has a version of one of your  gems  more  specific  to
-       your platform.
-
-       This  problem  is  also	not  limited to the 1m"java" 22mplatform. A similar
-       (common) problem can happen when developing on Windows and deploying to
-       Linux, or even when developing on OSX and deploying to Linux.
-
-       If  you know for sure that the gems packaged in 1mvendor/cache 22mare appro-
-       priate for the platform you are on, you can run 1mbundle install  --local0m
-       to  skip  checking  for more appropriate gems, and use the ones in 1mven-0m
-       1mdor/cache22m.
-
-       One way to be sure that you have the right platformed versions  of  all
-       your gems is to run 1mbundle package 22mon an identical machine and check in
-       the gems. For instance, you can run  1mbundle  package  22mon  an  identical
-       staging	box during your staging process, and check in the 1mvendor/cache0m
-       before deploying to production.
-
-
-
-				 October 2016		     BUNDLE-PACKAGE(1)

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

@@ -1,57 +0,0 @@
-BUNDLE-PLATFORM(1)					    BUNDLE-PLATFORM(1)
-
-
-
-1mNAME0m
-       1mbundle-platform 22m- Displays platform compatibility information
-
-1mSYNOPSIS0m
-       1mbundle platform 22m[--ruby]
-
-1mDESCRIPTION0m
-       1mplatform  22mwill display information from your Gemfile, Gemfile.lock, and
-       Ruby VM about your platform.
-
-       For instance, using this Gemfile(5):
-
-
-
-	   source "https://rubygems.org"
-
-	   ruby "1.9.3"
-
-	   gem "rack"
-
-
-
-       If you run 1mbundle platform 22mon Ruby 1.9.3, it will display the following
-       output:
-
-
-
-	   Your platform is: x86_64-linux
-
-	   Your app has gems that work on these platforms:
-	   * ruby
-
-	   Your Gemfile specifies a Ruby version requirement:
-	   * ruby 1.9.3
-
-	   Your current platform satisfies the Ruby version requirement.
-
-
-
-       1mplatform  22mwill  list  all the platforms in your 1mGemfile.lock 22mas well as
-       the 1mruby 22mdirective if applicable from your Gemfile(5). It will also let
-       you know if the 1mruby 22mdirective requirement has been met. If 1mruby 22mdirec-
-       tive doesn't match the running Ruby VM, it will tell you what part does
-       not.
-
-1mOPTIONS0m
-       1m--ruby 22mIt  will  display  the  ruby directive information, so you don't
-	      have to parse it from the Gemfile(5).
-
-
-
-
-				 October 2016		    BUNDLE-PLATFORM(1)

data/lib/bundler/man/bundle-update

@@ -1,221 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "BUNDLE\-UPDATE" "1" "October 2016" "" ""
-.
-.SH "NAME"
-\fBbundle\-update\fR \- Update your gems to the latest available versions
-.
-.SH "SYNOPSIS"
-\fBbundle update\fR \fI*gems\fR [\-\-group=NAME] [\-\-source=NAME] [\-\-local] [\-\-ruby]
-.
-.SH "DESCRIPTION"
-Update the gems specified (all gems, if none are specified), ignoring the previously installed gems specified in the \fBGemfile\.lock\fR\. In general, you should use bundle install(1) \fIbundle\-install\.1\.html\fR to install the same exact gems and versions across machines\.
-.
-.P
-You would use \fBbundle update\fR to explicitly update the version of a gem\.
-.
-.SH "OPTIONS"
-.
-.TP
-\fB\-\-group=<name>\fR
-Only update the gems in the specified group\. For instance, you can update all gems in the development group with \fBbundle update \-\-group development\fR\. You can also call \fBbundle update rails \-\-group test\fR to update the rails gem and all gems in the test group, for example\.
-.
-.TP
-\fB\-\-source=<name>\fR
-The name of a \fB:git\fR or \fB:path\fR source used in the Gemfile(5)\. For instance, with a \fB:git\fR source of \fBhttp://github\.com/rails/rails\.git\fR, you would call \fBbundle update \-\-source rails\fR
-.
-.TP
-\fB\-\-local\fR
-Do not attempt to fetch gems remotely and use the gem cache instead\.
-.
-.TP
-\fB\-\-ruby\fR
-Update the locked version of Ruby to the current version of Ruby\.
-.
-.TP
-\fB\-\-bundler\fR
-Update the locked version of bundler to the invoked bundler version\.
-.
-.SH "UPDATING ALL GEMS"
-If you run \fBbundle update\fR with no parameters, bundler will ignore any previously installed gems and resolve all dependencies again based on the latest versions of all gems available in the sources\.
-.
-.P
-Consider the following Gemfile(5):
-.
-.IP "" 4
-.
-.nf
-
-source "https://rubygems\.org"
-
-gem "rails", "3\.0\.0\.rc"
-gem "nokogiri"
-.
-.fi
-.
-.IP "" 0
-.
-.P
-When you run bundle install(1) \fIbundle\-install\.1\.html\fR the first time, bundler will resolve all of the dependencies, all the way down, and install what you need:
-.
-.IP "" 4
-.
-.nf
-
-Fetching gem metadata from https://rubygems\.org/\.\.\.\.\.\.\.\.\.
-Resolving dependencies\.\.\.
-Installing builder 2\.1\.2
-Installing abstract 1\.0\.0
-Installing rack 1\.2\.8
-Using bundler 1\.7\.6
-Installing rake 10\.4\.0
-Installing polyglot 0\.3\.5
-Installing mime\-types 1\.25\.1
-Installing i18n 0\.4\.2
-Installing mini_portile 0\.6\.1
-Installing tzinfo 0\.3\.42
-Installing rack\-mount 0\.6\.14
-Installing rack\-test 0\.5\.7
-Installing treetop 1\.4\.15
-Installing thor 0\.14\.6
-Installing activesupport 3\.0\.0\.rc
-Installing erubis 2\.6\.6
-Installing activemodel 3\.0\.0\.rc
-Installing arel 0\.4\.0
-Installing mail 2\.2\.20
-Installing activeresource 3\.0\.0\.rc
-Installing actionpack 3\.0\.0\.rc
-Installing activerecord 3\.0\.0\.rc
-Installing actionmailer 3\.0\.0\.rc
-Installing railties 3\.0\.0\.rc
-Installing rails 3\.0\.0\.rc
-Installing nokogiri 1\.6\.5
-
-Bundle complete! 2 Gemfile dependencies, 26 gems total\.
-Use `bundle show [gemname]` to see where a bundled gem is installed\.
-.
-.fi
-.
-.IP "" 0
-.
-.P
-As you can see, even though you have two gems in the Gemfile(5), your application needs 26 different gems in order to run\. Bundler remembers the exact versions it installed in \fBGemfile\.lock\fR\. The next time you run bundle install(1) \fIbundle\-install\.1\.html\fR, bundler skips the dependency resolution and installs the same gems as it installed last time\.
-.
-.P
-After checking in the \fBGemfile\.lock\fR into version control and cloning it on another machine, running bundle install(1) \fIbundle\-install\.1\.html\fR will \fIstill\fR install the gems that you installed last time\. You don\'t need to worry that a new release of \fBerubis\fR or \fBmail\fR changes the gems you use\.
-.
-.P
-However, from time to time, you might want to update the gems you are using to the newest versions that still match the gems in your Gemfile(5)\.
-.
-.P
-To do this, run \fBbundle update\fR, which will ignore the \fBGemfile\.lock\fR, and resolve all the dependencies again\. Keep in mind that this process can result in a significantly different set of the 25 gems, based on the requirements of new gems that the gem authors released since the last time you ran \fBbundle update\fR\.
-.
-.SH "UPDATING A LIST OF GEMS"
-Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of the gems that you specified locked to the versions in the \fBGemfile\.lock\fR\.
-.
-.P
-For instance, in the scenario above, imagine that \fBnokogiri\fR releases version \fB1\.4\.4\fR, and you want to update it \fIwithout\fR updating Rails and all of its dependencies\. To do this, run \fBbundle update nokogiri\fR\.
-.
-.P
-Bundler will update \fBnokogiri\fR and any of its dependencies, but leave alone Rails and its dependencies\.
-.
-.SH "OVERLAPPING DEPENDENCIES"
-Sometimes, multiple gems declared in your Gemfile(5) are satisfied by the same second\-level dependency\. For instance, consider the case of \fBthin\fR and \fBrack\-perftools\-profiler\fR\.
-.
-.IP "" 4
-.
-.nf
-
-source "https://rubygems\.org"
-
-gem "thin"
-gem "rack\-perftools\-profiler"
-.
-.fi
-.
-.IP "" 0
-.
-.P
-The \fBthin\fR gem depends on \fBrack >= 1\.0\fR, while \fBrack\-perftools\-profiler\fR depends on \fBrack ~> 1\.0\fR\. If you run bundle install, you get:
-.
-.IP "" 4
-.
-.nf
-
-Fetching source index for https://rubygems\.org/
-Installing daemons (1\.1\.0)
-Installing eventmachine (0\.12\.10) with native extensions
-Installing open4 (1\.0\.1)
-Installing perftools\.rb (0\.4\.7) with native extensions
-Installing rack (1\.2\.1)
-Installing rack\-perftools_profiler (0\.0\.2)
-Installing thin (1\.2\.7) with native extensions
-Using bundler (1\.0\.0\.rc\.3)
-.
-.fi
-.
-.IP "" 0
-.
-.P
-In this case, the two gems have their own set of dependencies, but they share \fBrack\fR in common\. If you run \fBbundle update thin\fR, bundler will update \fBdaemons\fR, \fBeventmachine\fR and \fBrack\fR, which are dependencies of \fBthin\fR, but not \fBopen4\fR or \fBperftools\.rb\fR, which are dependencies of \fBrack\-perftools_profiler\fR\. Note that \fBbundle update thin\fR will update \fBrack\fR even though it\'s \fIalso\fR a dependency of \fBrack\-perftools_profiler\fR\.
-.
-.P
-\fBIn short\fR, when you update a gem using \fBbundle update\fR, bundler will update all dependencies of that gem, including those that are also dependencies of another gem\.
-.
-.P
-In this scenario, updating the \fBthin\fR version manually in the Gemfile(5), and then running bundle install(1) \fIbundle\-install\.1\.html\fR will only update \fBdaemons\fR and \fBeventmachine\fR, but not \fBrack\fR\. For more information, see the \fBCONSERVATIVE UPDATING\fR section of bundle install(1) \fIbundle\-install\.1\.html\fR\.
-.
-.SH "RECOMMENDED WORKFLOW"
-In general, when working with an application managed with bundler, you should use the following workflow:
-.
-.IP "\(bu" 4
-After you create your Gemfile(5) for the first time, run
-.
-.IP
-$ bundle install
-.
-.IP "\(bu" 4
-Check the resulting \fBGemfile\.lock\fR into version control
-.
-.IP
-$ git add Gemfile\.lock
-.
-.IP "\(bu" 4
-When checking out this repository on another development machine, run
-.
-.IP
-$ bundle install
-.
-.IP "\(bu" 4
-When checking out this repository on a deployment machine, run
-.
-.IP
-$ bundle install \-\-deployment
-.
-.IP "\(bu" 4
-After changing the Gemfile(5) to reflect a new or update dependency, run
-.
-.IP
-$ bundle install
-.
-.IP "\(bu" 4
-Make sure to check the updated \fBGemfile\.lock\fR into version control
-.
-.IP
-$ git add Gemfile\.lock
-.
-.IP "\(bu" 4
-If bundle install(1) \fIbundle\-install\.1\.html\fR reports a conflict, manually update the specific gems that you changed in the Gemfile(5)
-.
-.IP
-$ bundle update rails thin
-.
-.IP "\(bu" 4
-If you want to update all the gems to the latest possible versions that still match the gems listed in the Gemfile(5), run
-.
-.IP
-$ bundle update
-.
-.IP "" 0
-

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

@@ -1,227 +0,0 @@
-BUNDLE-UPDATE(1)					      BUNDLE-UPDATE(1)
-
-
-
-1mNAME0m
-       1mbundle-update 22m- Update your gems to the latest available versions
-
-1mSYNOPSIS0m
-       1mbundle update 4m22m*gems24m [--group=NAME] [--source=NAME] [--local] [--ruby]
-
-1mDESCRIPTION0m
-       Update  the  gems specified (all gems, if none are specified), ignoring
-       the previously installed gems specified in the  1mGemfile.lock22m.  In  gen-
-       eral, you should use bundle install(1) 4mbundle-install.1.html24m to install
-       the same exact gems and versions across machines.
-
-       You would use 1mbundle update 22mto explicitly update the version of a gem.
-
-1mOPTIONS0m
-       1m--group=<name>0m
-	      Only update the gems in the specified group. For	instance,  you
-	      can  update all gems in the development group with 1mbundle update0m
-	      1m--group development22m. You  can  also	call  1mbundle	update	rails0m
-	      1m--group  test  22mto  update the rails gem and all gems in the test
-	      group, for example.
-
-       1m--source=<name>0m
-	      The name of a 1m:git 22mor 1m:path 22msource used in the	Gemfile(5).  For
-	      instance,        with	   a	    1m:git	 22msource	 of
-	      1mhttp://github.com/rails/rails.git22m, you would call 1mbundle  update0m
-	      1m--source rails0m
-
-       1m--local0m
-	      Do  not  attempt	to  fetch  gems remotely and use the gem cache
-	      instead.
-
-       1m--ruby 22mUpdate the locked version of Ruby  to  the  current	version  of
-	      Ruby.
-
-       1m--bundler0m
-	      Update the locked version of bundler to the invoked bundler ver-
-	      sion.
-
-1mUPDATING ALL GEMS0m
-       If you run 1mbundle update 22mwith no parameters, bundler  will	ignore	any
-       previously  installed  gems and resolve all dependencies again based on
-       the latest versions of all gems available in the sources.
-
-       Consider the following Gemfile(5):
-
-
-
-	   source "https://rubygems.org"
-
-	   gem "rails", "3.0.0.rc"
-	   gem "nokogiri"
-
-
-
-       When you run bundle install(1) 4mbundle-install.1.html24m  the  first  time,
-       bundler	will  resolve  all  of the dependencies, all the way down, and
-       install what you need:
-
-
-
-	   Fetching gem metadata from https://rubygems.org/.........
-	   Resolving dependencies...
-	   Installing builder 2.1.2
-	   Installing abstract 1.0.0
-	   Installing rack 1.2.8
-	   Using bundler 1.7.6
-	   Installing rake 10.4.0
-	   Installing polyglot 0.3.5
-	   Installing mime-types 1.25.1
-	   Installing i18n 0.4.2
-	   Installing mini_portile 0.6.1
-	   Installing tzinfo 0.3.42
-	   Installing rack-mount 0.6.14
-	   Installing rack-test 0.5.7
-	   Installing treetop 1.4.15
-	   Installing thor 0.14.6
-	   Installing activesupport 3.0.0.rc
-	   Installing erubis 2.6.6
-	   Installing activemodel 3.0.0.rc
-	   Installing arel 0.4.0
-	   Installing mail 2.2.20
-	   Installing activeresource 3.0.0.rc
-	   Installing actionpack 3.0.0.rc
-	   Installing activerecord 3.0.0.rc
-	   Installing actionmailer 3.0.0.rc
-	   Installing railties 3.0.0.rc
-	   Installing rails 3.0.0.rc
-	   Installing nokogiri 1.6.5
-
-	   Bundle complete! 2 Gemfile dependencies, 26 gems total.
-	   Use `bundle show [gemname]` to see where a bundled gem is installed.
-
-
-
-       As you can see, even though you have two gems in the  Gemfile(5),  your
-       application  needs 26 different gems in order to run. Bundler remembers
-       the exact versions it installed in 1mGemfile.lock22m. The next time you	run
-       bundle  install(1)  4mbundle-install.1.html24m, bundler skips the dependency
-       resolution and installs the same gems as it installed last time.
-
-       After checking in the 1mGemfile.lock 22minto version control and cloning  it
-       on  another  machine,  running  bundle install(1) 4mbundle-install.1.html0m
-       will 4mstill24m install the gems that you installed  last  time.  You  don't
-       need to worry that a new release of 1merubis 22mor 1mmail 22mchanges the gems you
-       use.
-
-       However, from time to time, you might want to update the gems  you  are
-       using  to  the  newest  versions that still match the gems in your Gem-
-       file(5).
-
-       To do this, run 1mbundle update22m, which will ignore the 1mGemfile.lock22m,  and
-       resolve	all the dependencies again. Keep in mind that this process can
-       result in a significantly different set of the 25 gems,	based  on  the
-       requirements  of  new gems that the gem authors released since the last
-       time you ran 1mbundle update22m.
-
-1mUPDATING A LIST OF GEMS0m
-       Sometimes, you want to update a single gem in the Gemfile(5), and leave
-       the  rest  of the gems that you specified locked to the versions in the
-       1mGemfile.lock22m.
-
-       For instance, in the scenario above,  imagine  that  1mnokogiri	22mreleases
-       version 1m1.4.422m, and you want to update it 4mwithout24m updating Rails and all
-       of its dependencies. To do this, run 1mbundle update nokogiri22m.
-
-       Bundler will update 1mnokogiri 22mand any of  its  dependencies,  but  leave
-       alone Rails and its dependencies.
-
-1mOVERLAPPING DEPENDENCIES0m
-       Sometimes,  multiple  gems declared in your Gemfile(5) are satisfied by
-       the same second-level dependency. For instance, consider  the  case  of
-       1mthin 22mand 1mrack-perftools-profiler22m.
-
-
-
-	   source "https://rubygems.org"
-
-	   gem "thin"
-	   gem "rack-perftools-profiler"
-
-
-
-       The  1mthin  22mgem  depends  on  1mrack >= 1.022m, while 1mrack-perftools-profiler0m
-       depends on 1mrack ~> 1.022m. If you run bundle install, you get:
-
-
-
-	   Fetching source index for https://rubygems.org/
-	   Installing daemons (1.1.0)
-	   Installing eventmachine (0.12.10) with native extensions
-	   Installing open4 (1.0.1)
-	   Installing perftools.rb (0.4.7) with native extensions
-	   Installing rack (1.2.1)
-	   Installing rack-perftools_profiler (0.0.2)
-	   Installing thin (1.2.7) with native extensions
-	   Using bundler (1.0.0.rc.3)
-
-
-
-       In this case, the two gems have their own set of dependencies, but they
-       share  1mrack  22min  common.  If  you  run 1mbundle update thin22m, bundler will
-       update 1mdaemons22m, 1meventmachine 22mand 1mrack22m, which are dependencies of	1mthin22m,
-       but   not   1mopen4   22mor   1mperftools.rb22m,   which   are	dependencies  of
-       1mrack-perftools_profiler22m. Note that 1mbundle update thin 22mwill update  1mrack0m
-       even though it's 4malso24m a dependency of 1mrack-perftools_profiler22m.
-
-       1mIn  short22m,	when  you  update  a  gem using 1mbundle update22m, bundler will
-       update all dependencies of that gem,  including	those  that  are  also
-       dependencies of another gem.
-
-       In this scenario, updating the 1mthin 22mversion manually in the Gemfile(5),
-       and then running  bundle  install(1)  4mbundle-install.1.html24m  will  only
-       update  1mdaemons  22mand  1meventmachine22m, but not 1mrack22m. For more information,
-       see  the  1mCONSERVATIVE  UPDATING  22msection  of  bundle  install(1)  4mbun-0m
-       4mdle-install.1.html24m.
-
-1mRECOMMENDED WORKFLOW0m
-       In  general, when working with an application managed with bundler, you
-       should use the following workflow:
-
-       o   After you create your Gemfile(5) for the first time, run
-
-	   $ bundle install
-
-       o   Check the resulting 1mGemfile.lock 22minto version control
-
-	   $ git add Gemfile.lock
-
-       o   When checking out this repository on another  development  machine,
-	   run
-
-	   $ bundle install
-
-       o   When checking out this repository on a deployment machine, run
-
-	   $ bundle install --deployment
-
-       o   After  changing  the  Gemfile(5)  to reflect a new or update depen-
-	   dency, run
-
-	   $ bundle install
-
-       o   Make sure to check the updated 1mGemfile.lock 22minto version control
-
-	   $ git add Gemfile.lock
-
-       o   If bundle install(1) 4mbundle-install.1.html24m reports a conflict, man-
-	   ually update the specific gems that you changed in the Gemfile(5)
-
-	   $ bundle update rails thin
-
-       o   If  you want to update all the gems to the latest possible versions
-	   that still match the gems listed in the Gemfile(5), run
-
-	   $ bundle update
-
-
-
-
-
-
-				 October 2016		      BUNDLE-UPDATE(1)