Bug #16266
closed
Additional empty folders created in lib/ruby/gems/2.7.0/gems by make install
Added by MSP-Greg (Greg L) over 4 years ago.
Updated about 4 years ago.
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
- 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?
Sorry, but code that creates thirty empty folders is just wrong, regardless of whether it creates 'problems'...
- Status changed from Feedback to Assigned
- Assignee set to hsbt (Hiroshi SHIBATA)
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.
- Status changed from Assigned to Rejected
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0