Project

General

Profile

Bug #16266

Additional empty folders created in lib/ruby/gems/2.7.0/gems by make install

Added by MSP-Greg (Greg L) about 1 month ago. Updated about 1 month ago.

Status:
Assigned
Priority:
Normal
Target version:
-
[ruby-core:95441]

Description

See https://github.com/ruby/ruby/pull/2580

Duplicating a comment there:

Somewhere between the following two commits, make install adds additional empty folders that are created in lib/ruby/gems/2.7.0/gems, most are default gems.

2019-08-23 9ffb0548bf good
2019-08-23 3b55394b07 bad

History

Updated by jeremyevans0 (Jeremy Evans) about 1 month ago

  • Status changed from Open to Feedback

Looking at the commit, the addition of the empty folders appears to be intentional, to result in the same behavior as gem install --default. Can you explain what problems this causes?

Updated by MSP-Greg (Greg L) about 1 month ago

Sorry, but code that creates thirty empty folders is just wrong, regardless of whether it creates 'problems'...

#3

Updated by jeremyevans0 (Jeremy Evans) about 1 month ago

  • Assignee set to hsbt (Hiroshi SHIBATA)
  • Status changed from Feedback to Assigned

MSP-Greg (Greg L) wrote:

Sorry, but code that creates thirty empty folders is just wrong, regardless of whether it creates 'problems'...

I disagree that a change that creates thirty empty folders is wrong a priori. This change appears to be deliberate in order to ensure consistency. Assigning to hsbt (Hiroshi SHIBATA) to decide whether this should be closed.

Also available in: Atom PDF