mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
156079a85d
Previously they had slightly different behavior when combined with conservative updating flags. The correct behavior is the `--update-strict` option, so `--script` now does that, The `--update-strict` option is left there for now but I will deprecate it later. https://github.com/rubygems/rubygems/commit/ab42046229
31 lines
846 B
Groff
31 lines
846 B
Groff
.\" generated with Ronn/v0.7.3
|
|
.\" http://github.com/rtomayko/ronn/tree/0.7.3
|
|
.
|
|
.TH "BUNDLE\-REMOVE" "1" "March 2022" "" ""
|
|
.
|
|
.SH "NAME"
|
|
\fBbundle\-remove\fR \- Removes gems from the Gemfile
|
|
.
|
|
.SH "SYNOPSIS"
|
|
\fBbundle remove [GEM [GEM \.\.\.]] [\-\-install]\fR
|
|
.
|
|
.SH "DESCRIPTION"
|
|
Removes the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid\. If a gem cannot be removed, a warning is printed\. If a gem is already absent from the Gemfile, and error is raised\.
|
|
.
|
|
.SH "OPTIONS"
|
|
.
|
|
.TP
|
|
\fB\-\-install\fR
|
|
Runs \fBbundle install\fR after the given gems have been removed from the Gemfile, which ensures that both the lockfile and the installed gems on disk are also updated to remove the given gem(s)\.
|
|
.
|
|
.P
|
|
Example:
|
|
.
|
|
.P
|
|
bundle remove rails
|
|
.
|
|
.P
|
|
bundle remove rails rack
|
|
.
|
|
.P
|
|
bundle remove rails rack \-\-install
|