summaryrefslogtreecommitdiff
path: root/array.c
diff options
context:
space:
mode:
authorDavid Rodríguez <deivid.rodriguez@riseup.net>2023-10-26 18:44:20 +0200
committerHiroshi SHIBATA <hsbt@ruby-lang.org>2023-11-08 09:04:28 +0900
commit7f7a7f13ededda5c91d84c3493dc6ef3cec53d1a (patch)
treef3a8351a266cb8ce84111c8a1203886d2c6b7d98 /array.c
parent2d719cd1468334a3507e4194a173da743b9987d1 (diff)
[rubygems/rubygems] Don't show bug report template when GEM_HOME has no writable bit
Instead, don't check that at all and proceed. If something fails to be written inside GEM_HOME, we'll eventually fail with a proper permissions error. In addition to that, the writable bit in GEM_HOME is not even reliable, because only the immediate parent is actually checked when writing. For example, ``` $ mkdir -p foo/bar $ chmod -w foo $ touch foo/bar/baz # writes without issue ``` https://github.com/rubygems/rubygems/commit/4bced7ac73
Diffstat (limited to 'array.c')
0 files changed, 0 insertions, 0 deletions