Repository navigation
Replies: 2 comments
|
This issue makes it difficult / impossible to manage versions of rdoc with bundler in the normal way, unless you can tolerate 10-20 lines of warnings when doing bundler operations. The workaround is lock rdoc to the version that comes with your ruby. |
0 replies
|
Reposted as an issue (#9945) due to low activity in Discussions. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Posting a discussion as suggested by @tompng in ruby/rdoc#1609 (comment)
Problem
When the same gem is installed in multiple directories in
Gem.path, RubyGems loads its plugin once per directory rather than once per gem.Possible fix
RubyGems should load at most one plugin for a given gem name.
Gem.load_pluginscould deduplicate plugins by gem name and select the plugin associated with the activated gem specification, or otherwise apply RubyGems’ normal gem-selection rules.Questions for community and maintainers:
Elaboration
For example:
Both contain RDoc, including its RubyGems plugin:
RubyGems loads both plugin files, producing warnings such as:
RDoc is the only bundled gem currently shipping a RubyGems plugin, so it is the only bundled gem exposing the problem.
Pinning RDoc does not solve the underlying issue: the warning also occurs when different RDoc versions are installed, and potentially when the same version exists in multiple locations.
All reactions