." generated with nRonn/v0.11.1 ." github.com/n-ronn/nronn/tree/0.11.1 .TH “BUNDLE-INSTALL” “1” “October 2024” “” .SH “NAME” fBbundle-installfR - Install the dependencies specified in your Gemfile .SH “SYNOPSIS” fBbundle installfR [--binstubs] [--clean] [--deployment] [--frozen] [--full-index] [--gemfile=GEMFILE] [--jobs=NUMBER] [--local] [--no-cache] [--no-prune] [--path PATH] [--prefer-local] [--quiet] [--redownload] [--retry=NUMBER] [--shebang] [--standalone[=GROUP[ GROUP|.|.|.]]] [--system] [--trust-policy=POLICY] [--with=GROUP[ GROUP|.|.|.]] [--without=GROUP[ GROUP|.|.|.]] .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” The fB--cleanfR, fB--deploymentfR, fB--frozenfR, fB--no-prunefR, fB--pathfR, fB--shebangfR, fB--systemfR, fB--withoutfR and fB--withfR options are deprecated because they only make sense if they are applied to every subsequent fBbundle installfR run automatically and that requires fBbundlerfR to silently remember them. Since fBbundlerfR will no longer remember CLI flags in future versions, fBbundle configfR (see bundle-config(1)) should be used to apply them permanently. .TP fB--binstubs[=]fR Makes a bundle that can work without depending on Rubygems or Bundler at runtime. A space separated list of groups to install has to be specified. Bundler creates a directory named fBbundlefR and installs the bundle there. It also generates a fBbundle/bundler/setup.rbfR file to replace Bundler’s own setup in the manner required. Using this option implicitly sets fBpathfR, which is a [remembered option][REMEMBERED OPTIONS]. .TP fB--systemfR Installs the gems specified in the bundle to the system’s Rubygems location. This overrides any previous configuration of fB--pathfR. .IP This option is deprecated in favor of the fBsystemfR setting. .TP fB--trust-policy=[
gem ‘sinatra’
group :production do
gem 'rack\-perftools\-profiler'
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 the gems you list in your Gemfile(5), and can (surprisingly) radically change the gems you are using. .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, in both applications and gems. 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. .P When Bundler first shipped, the fBGemfile.lockfR was included in the fB.gitignorefR file included with generated gems. Over time, however, it became clear that this practice forces the pain of broken dependencies onto new contributors, while leaving existing contributors potentially unaware of the problem. Since fBbundle installfR is usually the first step towards a contribution, the pain of broken dependencies would discourage new contributors from contributing. As a result, we have revised our guidance for gem authors to now recommend checking in the lock for gems. .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 gem in the Gemfile(5) is 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 fIguides.rubygems.org/rubygems-basics/#installing-gemsfR .IP “(bu” 4 Rubygems signing docs fIguides.rubygems.org/security/fR .IP “” 0