Go to main content

man pages section 1: User Commands

Exit Print View

Updated: Thursday, June 13, 2019
 
 

bundle-lock (1)

Name

bundle-lock - Man page for 'bundle-lock' in section 1

Synopsis

Please see following description for synopsis

Description

TH  "BUNDLE-LOCK" "1" "November 2018" "" "" SH "NAME" bundle-lock
- Creates / Updates a lockfile without installing  SH  "SYNOPSIS"
bundle  lock  [--update]  [--local]  [--print]  [--lockfile=PATH]
[--full-index]  [--add-platform]  [--remove-platform]   [--patch]
[--minor]  [--major] [--strict] [--conservative] SH "DESCRIPTION"
Lock the gems  specified  in  Gemfile.   SH  "OPTIONS"  TP  --up-
date=<*gems>  Ignores the existing lockfile. Resolve then updates
lockfile. Taking a list of gems or updating all gems if  no  list
is  given.  TP --local Do not attempt to connect to rubygems.org.
Instead, Bundler will use the gems already present  in  Rubygems'
cache  or  in  vendor/cache.  Note  that  if  a appropriate plat-
form-specific gem exists on rubygems.org it will  not  be  found.
TP  --print  Prints  the lockfile to STDOUT instead of writing to
the file system.  TP --lockfile=<path> The path where  the  lock-
file  should  be  written to.  TP --full-index Fall back to using
the single-file index of all gems.  TP --add-platform Add  a  new
platform  to  the lockfile, re-resolving for the addition of that
platform.  TP --remove-platform Remove a platform from the  lock-
file.  TP --patch If updating, prefer updating only to next patch
version.  TP --minor If updating, prefer updating  only  to  next
minor  version.   TP --major If updating, prefer updating to next
major version (default).  TP --strict If updating, do  not  allow
any  gem  to  be updated past latest --patch | --minor | --major.
TP --conservative If updating, use  bundle  install  conservative
update behavior and do not allow shared dependencies to be updat-
ed.  SH "UPDATING ALL GEMS" If you run bundle lock with  --update
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 "UPDAT-
ING 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 Gemfile.lock.  P For instance,  you
only  want to update nokogiri, run bundle lock --update nokogiri.
P Bundler will update nokogiri and any of its  dependencies,  but
leave  the rest of the gems that you specified locked to the ver-
sions in the Gemfile.lock.  SH "SUPPORTING  OTHER  PLATFORMS"  If
you  want  your  bundle  to  support platforms other than the one
you're running locally, you can run  bundle  lock  --add-platform
PLATFORM to add PLATFORM to the lockfile, force bundler to re-re-
solve and consider the new platform when picking gems, all  with-
out  needing to have a machine that matches PLATFORM handy to in-
stall those platform-specific gems on.  P For a full  explanation
of  gem  platforms,  see  gem help platform.  SH "PATCH LEVEL OP-
TIONS" See bundle update(1) bundle-update.1.html for details.


See for descriptions of the following attributes:

+---------------+------------------+
|ATTRIBUTE TYPE | ATTRIBUTE VALUE  |
+---------------+------------------+
|Availability   | runtime/ruby-26  |
+---------------+------------------+
|Stability      | Uncommitted      |
+---------------+------------------+

This   software   was   built   from    source    available    at
https://github.com/oracle/solaris-userland.   The original commu-
nity   source    was    downloaded    from     http://cache.ruby-
lang.org/pub/ruby/2.6/ruby-2.6.0.tar.gz

Further  information about this software can be found on the open
source community website at http://www.ruby-lang.org/.