." generated with Ronn/v0.7.3 ." github.com/rtomayko/ronn/tree/0.7.3 . .TH “BUNDLE-INSTALL” “1” “July 2014” “” “” . .SH “NAME” fBbundle-installfR - Install the dependencies specified in your Gemfile . .SH “SYNOPSIS” fBbundle installfR [--gemfile=GEMFILE] . .IP “” 4 . .nf
[\-\-path PATH] [\-\-system] [\-\-without=GROUP1[ GROUP2\.\.\.]] [\-\-local] [\-\-deployment] [\-\-binstubs[=DIRECTORY]] [\-\-standalone[=GROUP1[ GROUP2\.\.\.]]] [\-\-trust\-policy=POLICY] [\-\-jobs=SIZE] [\-\-retry=TRIES] [\-\-no\-cache] [\-\-quiet] [\-\-clean] [\-\-full\-index] [\-\-no\-prune] [\-\-shebang]
. .fi . .IP “” 0 . .SH “DESCRIPTION” Install the gems specified in your
Gemfile(5). If this is the first time you run bundle install (and a
fBGemfile.lockfR does not exist), bundler will fetch all remote sources,
resolve dependencies and install all needed gems. . .P If a
fBGemfile.lockfR does exist, and you have not updated your Gemfile(5),
bundler will fetch all remote sources, but use the dependencies specified
in the fBGemfile.lockfR instead of resolving dependencies. . .P If a
fBGemfile.lockfR does exist, and you have updated your Gemfile(5), bundler
will use the dependencies in the fBGemfile.lockfR for all gems that you did
not update, but will re-resolve the dependencies of gems that you did
update. You can find more information about this update process below under
fICONSERVATIVE UPDATINGfR. . .SH “OPTIONS” . .TP
fB--gemfile=<gemfile>fR The location of the Gemfile(5) that bundler
should use. This defaults to a gemfile in the current working directory. In
general, bundler will assume that the location of the Gemfile(5) is also
the project root, and will look for the fBGemfile.lockfR and
fBvendor/cachefR relative to it. . .TP fB--path=<path>fR The location
to install the gems in the bundle to. This defaults to Rubygems' gem home,
which is also the default location where fBgem installfR installs gems.
This means that, by default, gems installed without a fB--pathfR setting
will show up in fBgem listfR. This setting is a fIremembered optionfR. .
.TP fB--systemfR Installs the gems in the bundle to the system location.
This overrides any previous fIrememberedfR use of fB--pathfR. . .TP
fB--without=<list>fR A space-separated list of groups to skip
installing. This is a fIremembered optionfR. . .TP fB--localfR Do not
attempt to connect to fBrubygems.orgfR, instead using just the gems already
present in Rubygems' cache or in fBvendor/cachefR. Note that if a more
appropriate platform-specific gem exists on fBrubygems.orgfR, it will not
be found. . .TP fB--deploymentfR Switches bundler's defaults into
fIdeployment modefR. Do not use this flag on development machines. . .TP
fB--binstubs[= source “rubygems.org” gem “sinatra” group :production do end . .fi . .IP “” 0 . .P In this case, fBsinatrafR depends on any version
of Rack (fB>= 1.0fR, while fBrack-perftools-profilerfR depends on 1.x
(fB~> 1.0fR). . .P When you run fBbundle install --without productionfR
in development, we look at the dependencies of fBrack-perftools-profilerfR
as well. That way, you do not spend all your time developing against Rack
2.0, using new APIs unavailable in Rack 1.x, only to have bundler switch to
Rack 1.2 when the fBproductionfR group fIisfR used. . .P This should not
cause any problems in practice, because we do not attempt to fBinstallfR
the gems in the excluded groups, and only evaluate as part of the
dependency resolution process. . .P This also means that you cannot include
different versions of the same gem in different groups, because doing so
would result in different sets of dependencies used in development and
production. Because of the vagaries of the dependency resolution process,
this usually affects more than just the gems you list in your Gemfile(5),
and can (surprisingly) radically change the gems you are using. . .SH
“REMEMBERED OPTIONS” Some options (marked above in the fIOPTIONSfR section)
are remembered between calls to fBbundle installfR, and by the Bundler runtime. . .P For instance, if you
run fBbundle install --without testfR, a subsequent call to fBbundle
installfR that does not include a fB--withoutfR flag will remember your
previous choice. . .P In addition, a call to fBBundler.setupfR will not
attempt to make the gems in those groups available on the Ruby load path,
as they were not installed. . .P The settings that are remembered are: .
.TP fB--deploymentfR At runtime, this remembered setting will also result
in Bundler raising an exception if the
fBGemfile.lockfR is out of date. . .TP fB--pathfR Subsequent calls to
fBbundle installfR will install gems to the directory originally passed to
fB--pathfR. The Bundler runtime will
look for gems in that location. You can revert this option by running
fBbundle install --systemfR. . .TP fB--binstubsfR Bundler will update the executables every
subsequent call to fBbundle installfR. . .TP fB--withoutfR As described
above, Bundler will skip the gems
specified by fB--withoutfR in subsequent calls to fBbundle installfR. The
Bundler runtime will also not try to
make the gems in the skipped groups available. . .SH “THE GEMFILE.LOCK”
When you run fBbundle installfR, Bundler will persist the full names and
versions of all gems that you used (including dependencies of the gems
specified in the Gemfile(5)) into a file called fBGemfile.lockfR. . .P Bundler uses this file in all subsequent
calls to fBbundle installfR, which guarantees that you always use the same
exact code, even as your application moves across machines. . .P Because of
the way dependency resolution works, even a seemingly small change (for
instance, an update to a point-release of a dependency of a gem in your
Gemfile(5)) can result in radically different gems being needed to satisfy
all dependencies. . .P As a result, you fBSHOULDfR check your
fBGemfile.lockfR into version control. If you do not, every machine that
checks out your repository (including your production server) will resolve
all dependencies again, which will result in different versions of
third-party code being used if fBanyfR of the gems in the Gemfile(5) or any
of their dependencies have been updated. . .SH “CONSERVATIVE UPDATING” When
you make a change to the Gemfile(5) and then run fBbundle installfR, Bundler will update only the gems that you
modified. . .P In other words, if a gem that you fBdid not modifyfR worked
before you called fBbundle installfR, it will continue to use the exact
same versions of all dependencies as it used before the update. . .P Let's
take a look at an example. Here's your original Gemfile(5): . .IP “” 4 .
.nf source “rubygems.org” gem “actionpack”, “2.3.8” gem “activemerchant” . .fi . .IP “” 0 . .P In
this case, both fBactionpackfR and fBactivemerchantfR depend on
fBactivesupportfR. The fBactionpackfR gem depends on fBactivesupport
2.3.8fR and fBrack ~> 1.1.0fR, while the fBactivemerchantfR gem depends
on fBactivesupport >= 2.3.2fR, fBbraintree >= 2.0.0fR, and fBbuilder
>= 2.0.0fR. . .P When the dependencies are first resolved, Bundler will select fBactivesupport
2.3.8fR, which satisfies the requirements of both gems in your Gemfile(5).
. .P Next, you modify your Gemfile(5) to: . .IP “” 4 . .nf source “rubygems.org” gem “actionpack”, “3.0.0.rc” gem “activemerchant” . .fi . .IP “” 0 . .P The
fBactionpack 3.0.0.rcfR gem has a number of new dependencies, and updates
the fBactivesupportfR dependency to fB= 3.0.0.rcfR and the fBrackfR
dependency to fB~> 1.2.1fR. . .P When you run fBbundle installfR, Bundler notices that you changed the
fBactionpackfR gem, but not the fBactivemerchantfR gem. It evaluates the
gems currently being used to satisfy its requirements: . .TP
fBactivesupport 2.3.8fR also used to satisfy a dependency in
fBactivemerchantfR, which is not being updated . .TP fBrack ~> 1.1.0fR
not currently being used to satisfy another dependency . .P Because you did
not explicitly ask to update fBactivemerchantfR, you would not expect it to
suddenly stop working after updating fBactionpackfR. However, satisfying
the new fBactivesupport 3.0.0.rcfR dependency of actionpack requires
updating one of its dependencies. . .P Even though fBactivemerchantfR
declares a very loose dependency that theoretically matches fBactivesupport
3.0.0.rcfR, bundler treats gems in your Gemfile(5) that have not changed as
an atomic unit together with their dependencies. In this case, the
fBactivemerchantfR dependency is treated as fBactivemerchant 1.7.1 +
activesupport 2.3.8fR, so fBbundle installfR will report that it cannot
update fBactionpackfR. . .P To explicitly update fBactionpackfR, including
its dependencies which other gems in the Gemfile(5) still depend on, run
fBbundle update actionpackfR (see fBbundle update(1)fR). . .P fBSummaryfR:
In general, after making a change to the Gemfile(5) , you should first try
to run fBbundle installfR, which will guarantee that no other gems in the
Gemfile(5) are impacted by the change. If that does not work, run bundle
update(1) fIbundle-update.1.htmlfR. . .SH “SEE ALSO” . .IP “(bu” 4 Gem install docs: guides.rubygems.org/rubygems-basics/#installing-gems
. .IP “(bu” 4 Rubygems signing docs: guides.rubygems.org/security/
. .IP “” 0]fR Make a bundle that can work without Ruby
Gems or Bundler at runtime. It takes a
space separated list of groups to install. It creates a fBbundlefR
directory and installs the bundle there. It also generates a
fBbundle/bundler/setup.rbfR file to replace Bundler's own setup. . .TP
fB--trust-policy=[
gem "rack\-perftools\-profiler"
Generated with the Darkfish Rdoc Generator 2.