Bug #10213: bundled gems ignored by make install

• Status: Feedback
• Assignee: hsbt (Hiroshi SHIBATA)
• Target version: -
• ruby -v: ruby 2.2.0dev (2014-09-08 trunk 47447) [x86_64-linux]
• Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
• Tags: notbug, build

[Hanmac (Hans Mackowiak)]

i am often working with ruby trunk, and then i notice that
"sudo make install" does ignore the gems that got moved from
"defs/default_gems" to "gems/bundled_gems"

means gems listed in "gems/bundled_gems" toally got ignored and might missing later

[Hanmac (Hans Mackowiak)]

EDIT: i forgot it might be good if there is a way to detect if a gem is installed as bundled like there is "Gem::Specification#default_gem?" for the default installed gems

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned
• Assignee changed from nobu (Nobuyoshi Nakada) to hsbt (Hiroshi SHIBATA)

[kou (Kouhei Sutou)]

Hans Mackowiak wrote:

EDIT: i forgot it might be good if there is a way to detect if a gem is installed as bundled like there is "Gem::Specification#default_gem?" for the default installed gems

Could you show us an use case when do you want to use the method?

Default gems work like normal gems. Bundled gems work as normal gems. So I think that we will not need to detect whether the gem is bundled gem or normal gem.

[Hanmac (Hans Mackowiak)]

a "Gem::Specification#bundled_gem?" would have been the same use case as a "Gem::Specification#default_gem?" i think ... hm currently you can remove bundled gems with "gem uninstall", i dont know if that is such a good idea because it might break something ... (thats why default gems are potected)

my use case would be i writing a script that makes a dot graph from the installed/requested gems and the dependencies between them ... with this some gems are different styled depending on some conditions, like if they have older versions that can be safe-removed(cleanup) or if there are newer versions online that can be updated, or if that gem is a default gem

[kou (Kouhei Sutou)]

Hans Mackowiak wrote:

my use case would be i writing a script that makes a dot graph from the installed/requested gems and the dependencies between them ... with this some gems are different styled depending on some conditions, like if they have older versions that can be safe-removed(cleanup) or if there are newer versions online that can be updated, or if that gem is a default gem

Thanks for describing your use case. It seems that Gem::Specification#bundled_gem? isn't needed for your use case. Because you can handle default gems as normal gems.

[mame (Yusuke Endoh)]

• Status changed from Assigned to Feedback

Maybe because of time, I cannot understand what is a problem. What do you mean "ignored"?

A bundled gem has been used for many years as a bare gem that is automatically installed during "make install" (i.e., it can be uninstalled), and I don't think that's particularly confusing. I think it would be rather confusing to give special treatment by introducing bundle_gem?.