[ruby-core:104011] [Ruby master Bug#17885] require_relative and require should be compatible with each other when symlinked files are used

Issue #17885 has been updated by john_firebaugh (John Firebaugh).


This causes [an issue with rules_ruby for Bazel](https://github.com/bazelruby/rules_ruby/issues/100). Bazel uses symlinks extensively to implement hermetic build sandboxing.

----------------------------------------
Bug #17885: require_relative and require should be compatible with each other when symlinked files are used
https://bugs.ruby-lang.org/issues/17885#change-92146

* Author: john_firebaugh (John Firebaugh)
* Status: Open
* Priority: Normal
* ruby -v: ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-darwin19]
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
This is similar to #10222 (which was fixed), but it's with symlinked files. #10222 was with symlinked directories.

If files are symlinked, then mixing `require` and `require_relative` can result in the same file being loaded twice.

```
mkdir a
echo "require_relative 'b'" > a/a.rb
echo "p 'b loaded'" > a/b.rb
mkdir b
ln -s ../a/a.rb b
ln -s ../a/b.rb b
echo "$: << File.expand_path('../b', __FILE__); require 'b'; require 'a'" > c.rb
ruby c.rb
```

Expected behavior is that this prints "b loaded" once. Actual behavior is that it prints "b loaded" twice.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>