You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ruby/rubygems] Add support for lockfile in Gemfile
This allows you to specify the lockfile to use. This is useful if
you want to use different lockfiles for different ruby versions or
platforms. You can also skip writing the lockfile by using a false
value.
ruby/rubygems@2896aa3fc2
Co-authored-by: Colby Swandale <996377+colby-swandale@users.noreply.github.com>
Copy file name to clipboardExpand all lines: lib/bundler/man/gemfile.5
+18-1Lines changed: 18 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -469,4 +469,21 @@ For implicit gems (dependencies of explicit gems), any source, git, or path repo
469
469
.IP"3."4
470
470
If neither of the above conditions are met, the global source will be used\. If multiple global sources are specified, they will be prioritized from last to first, but this is deprecated since Bundler 1\.13, so Bundler prints a warning and will abort with an error in the future\.
471
471
.IP""0
472
-
472
+
.SH "LOCKFILE"
473
+
By default, Bundler will create a lockfile by adding \fB\.lock\fR to the end of the Gemfile name\. To change this, use the \fBlockfile\fR method:
474
+
.IP""4
475
+
.nf
476
+
lockfile "/path/to/lockfile\.lock"
477
+
.fi
478
+
.IP""0
479
+
.P
480
+
This is useful when you want to use different lockfiles per ruby version or platform\.
481
+
.P
482
+
To avoid writing a lock file, use \fBfalse\fR as the argument:
483
+
.IP""4
484
+
.nf
485
+
lockfile false
486
+
.fi
487
+
.IP""0
488
+
.P
489
+
This is useful for library development and other situations where the code is expected to work with a range of dependency versions\.
0 commit comments