." generated with Ronn/v0.7.3 ." github.com/rtomayko/ronn/tree/0.7.3 . .TH “BUNDLE-LOCK” “1” “December 2015” “” “” . .SH “NAME” fBbundle-lockfR - Creates / Updates a lockfile without installing . .SH “SYNOPSIS” fBbundle lockfR [--update] . .IP “” 4 . .nf
[\-\-local] [\-\-print] [\-\-lockfile=PATH]
. .fi . .IP “” 0 . .SH “DESCRIPTION” Lock the gems specified in Gemfile. . .SH “OPTIONS” . .TP fB--update=<*gems>fR Ignores the existing lockfile. Resolve then updates lockfile. Taking a list of gems or updating all gems if no list is given. . .TP fB--localfR Do not attempt to connect to fBrubygems.orgfR. Instead, Bundler will use the gems already present in Rubygems' cache or in fBvendor/cachefR. Note that if a appropriate platform-specific gem exists on fBrubygems.orgfR it will not be found. . .TP fB--printfR Prints the lockfile to STDOUT instead of writing to the file system. . .TP fB--lockfile=<path>fR The path where the lockfile should be written to. . .SH “UPDATING ALL GEMS” If you run fBbundle lockfR with fB--updatefR option 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. . .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.lockfR. . .P For instance, you only want to update fBnokogirifR, run fBbundle lock --update nokogirifR. . .P Bundler will update fBnokogirifR and any of its dependencies, but leave the rest of the gems that you specified locked to the versions in the fBGemfile.lockfR.