From bbb8e91274de038c5d9c4f2869f07cd53c6b3025 Mon Sep 17 00:00:00 2001 From: Hiroshi SHIBATA Date: Tue, 28 Jul 2026 13:40:04 +0900 Subject: [PATCH 1/3] [ruby/rubygems] Clarify that Gemfile :path points to unpacked gem sources The :path option was misread as a way to install a packaged .gem file. State explicitly that it expects a directory with the gem's unpacked source code. https://github.com/ruby/rubygems/commit/dc7fdaa2a6 --- lib/bundler/man/gemfile.5.ronn | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/lib/bundler/man/gemfile.5.ronn b/lib/bundler/man/gemfile.5.ronn index dd5db5013fea30..a733ae866e040a 100644 --- a/lib/bundler/man/gemfile.5.ronn +++ b/lib/bundler/man/gemfile.5.ronn @@ -451,7 +451,9 @@ Since the `bitbucket` method is a specialization of `git_source`, it accepts a ` You can specify that a gem is located in a particular location on the file system. Relative paths are resolved relative to the -directory containing the `Gemfile`. +directory containing the `Gemfile`. The path must point to a +directory containing the gem's unpacked source code, not to a +packaged `.gem` file. Similar to the semantics of the `:git` option, the `:path` option requires that the directory in question either contains From 58cf248b6bdd0dda9db57f59ab8b0cec5c4e6474 Mon Sep 17 00:00:00 2001 From: Hiroshi SHIBATA Date: Tue, 28 Jul 2026 13:40:04 +0900 Subject: [PATCH 2/3] [ruby/rubygems] Link bundle-platform(1) to the PLATFORMS section of gemfile(5) The detailed explanation of platforms lives in gemfile(5), but bundle-platform(1) never pointed readers there. https://github.com/ruby/rubygems/commit/0af79d82ff --- lib/bundler/man/bundle-platform.1.ronn | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/lib/bundler/man/bundle-platform.1.ronn b/lib/bundler/man/bundle-platform.1.ronn index 744acd1b43a7fd..421be7df575f65 100644 --- a/lib/bundler/man/bundle-platform.1.ronn +++ b/lib/bundler/man/bundle-platform.1.ronn @@ -38,6 +38,9 @@ If you run `bundle platform` on Ruby 3.1.2, it displays the following output: if the `ruby` directive requirement has been met. If `ruby` directive doesn't match the running Ruby VM, it tells you what part does not. +For a detailed explanation of how bundler handles platforms, see the +`PLATFORMS` section in Gemfile(5). + ## OPTIONS * `--ruby`: @@ -47,3 +50,4 @@ match the running Ruby VM, it tells you what part does not. ## SEE ALSO * [bundle-lock(1)](bundle-lock.1.html) +* [Gemfile(5)](gemfile.5.html) From fdf6dba13dbb8b9c43b56c85ebd00e892d9ba0b3 Mon Sep 17 00:00:00 2001 From: Hiroshi SHIBATA Date: Tue, 28 Jul 2026 13:56:26 +0900 Subject: [PATCH 3/3] [ruby/rubygems] Regenerate man pages https://github.com/ruby/rubygems/commit/6c1bf4b7d1 --- lib/bundler/man/bundle-platform.1 | 4 ++++ lib/bundler/man/gemfile.5 | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/lib/bundler/man/bundle-platform.1 b/lib/bundler/man/bundle-platform.1 index 39b71112635311..a23dc459604b54 100644 --- a/lib/bundler/man/bundle-platform.1 +++ b/lib/bundler/man/bundle-platform.1 @@ -38,6 +38,8 @@ Your current platform satisfies the Ruby version requirement\. .IP "" 0 .P \fBplatform\fR lists all the platforms in your \fBGemfile\.lock\fR as well as the \fBruby\fR directive if applicable from your Gemfile(5)\. It also lets you know if the \fBruby\fR directive requirement has been met\. If \fBruby\fR directive doesn't match the running Ruby VM, it tells you what part does not\. +.P +For a detailed explanation of how bundler handles platforms, see the \fBPLATFORMS\fR section in Gemfile(5)\. .SH "OPTIONS" .TP \fB\-\-ruby\fR @@ -45,5 +47,7 @@ It will display the ruby directive information, so you don't have to parse it fr .SH "SEE ALSO" .IP "\(bu" 4 bundle\-lock(1) \fIbundle\-lock\.1\.html\fR +.IP "\(bu" 4 +Gemfile(5) \fIgemfile\.5\.html\fR .IP "" 0 diff --git a/lib/bundler/man/gemfile.5 b/lib/bundler/man/gemfile.5 index a4989e4a51c69b..20ae73f5db14d3 100644 --- a/lib/bundler/man/gemfile.5 +++ b/lib/bundler/man/gemfile.5 @@ -392,7 +392,7 @@ gem "rails", git: "https://rails@bitbucket\.org/rails/rails\.git" .P Since the \fBbitbucket\fR method is a specialization of \fBgit_source\fR, it accepts a \fB:branch\fR named argument\. .SS "PATH" -You can specify that a gem is located in a particular location on the file system\. Relative paths are resolved relative to the directory containing the \fBGemfile\fR\. +You can specify that a gem is located in a particular location on the file system\. Relative paths are resolved relative to the directory containing the \fBGemfile\fR\. The path must point to a directory containing the gem's unpacked source code, not to a packaged \fB\.gem\fR file\. .P Similar to the semantics of the \fB:git\fR option, the \fB:path\fR option requires that the directory in question either contains a \fB\.gemspec\fR for the gem, or that you specify an explicit version that bundler should use\. .P